NIST deprecates RSA-2048 from 2030. Find every one of them before attackers do.
☕
☕ Maven
Not in CISA KEV
HIGH severity

CVE-2022-43408 — pipeline-stage-view

HIGHFix: jenkinsci/pipeline-stage-view-plugin@cee2751

CVE-2022-43408 is a high-severity (CVSS 8) Cross-Site Request Forgery (CSRF) vulnerability in org.jenkins-ci.plugins.pipeline-stage-view:pipeline-stage-view. A fix is available for org.jenkins-ci.plugins.pipeline-stage-view:pipeline-stage-view — see the affected versions and patch details below.

Jenkins Pipeline: Stage View Plugin allows CSRF protection bypass of any target URL in Jenkins

Published
Updated
Affected
2 pkgs
Patched
2 / 2
Exploits
None indexed
Exploitation data as of Nov 5, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

Exploitation Status

No confirmed exploitation observed yet

  • CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.

Exploitation and automatability from CISA’s SSVC triage for CVE-2022-43408.

EPSS Exploitation Probability

via FIRST.org ↗
0.5%probability of exploitation in next 30 days
Lower Risk0.00%
Lower risk than most CVEs46th percentile — riskier than 46% of all scored CVEsHighest risk
0.00%0.35%0.70%1.04%0.0%0.5%May 26Sep 26Nov 26

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

How urgent is this, really

Where this sits among everything scored

Real-World Exposure

2 pkgs affected
☕org.jenkins-ci.plugins.pipeline-stage-view:pipeline-stage-view☕org.jenkins-ci.plugins.pipeline-stage-view:pipeline-stage-view

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects Maven packages — download data is not available via public APIs for these ecosystems.

Description

Jenkins Pipeline: Stage View Plugin provides a visualization of Pipeline builds. It also allows users to interact with input steps from Pipeline: Input Step Plugin.

Pipeline: Stage View Plugin 2.26 and earlier does not correctly encode the ID of input steps when using it to generate URLs to proceed or abort Pipeline builds.

This allows attackers able to configure Pipelines to specify input step IDs resulting in URLs that would bypass the CSRF protection of any target URL in Jenkins.

Pipeline: Stage View Plugin 2.27 correctly encodes the ID of input steps when using it to generate URLs to proceed or abort Pipeline builds.

Affected Packages

2 total 2 fixed
EcosystemPackageVulnerable rangeFix
☕Mavenorg.jenkins-ci.plugins.pipeline-stage-view:pipeline-stage-view≥ 2.25&&< 2.272.27org.jenkins-ci.plugins.pipeline-stage-view:pipeline-stage-view:2.27
☕Mavenorg.jenkins-ci.plugins.pipeline-stage-view:pipeline-stage-viewall versions2.24.2org.jenkins-ci.plugins.pipeline-stage-view:pipeline-stage-view:2.24.2

Affected Products

1 product · 1 configurations
Application
pipeline\jenkins
< 2.27
1 version
stage_view

Detection & mitigation playbook

Open-source dependency

  1. Detect

    Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for org.jenkins-ci.plugins.pipeline-stage-view:pipeline-stage-view, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

  2. Fix

    Update org.jenkins-ci.plugins.pipeline-stage-view:pipeline-stage-view to 2.27 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2022-43408 is resolved across your whole dependency graph.

  3. Workarounds

    If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

Fixing This On Your OS

If you run this on a Linux distribution, patch through your package manager against the distro's own security advisory below — it tracks the exact backported fix for your release, which can ship on a different timeline (and sometimes a different severity) than the upstream project.

Red HatModerate

Red Hat has shipped fixes for this vulnerability in OpenShift Container Platform versions 4.9 through 4.12 via updated jenkins-2-plugins packages. Older streams that have reached end of life are not being fixed.

Workaround published by Red Hat
Restrict the ability to configure Jenkins Pipelines to trusted users only. Upgrade to Jenkins Pipeline: Stage View Plugin version 2.27 or later, which correctly encodes input step IDs in generated URLs.
Source: Red Hat security advisory for CVE-2022-43408 (CC BY 4.0)
ProductFixed inAdvisory
OCP-Tools-4.12-RHEL-8jenkins-2-plugins-0:4.12.1675702407-1.el8RHSA-2023:1064
OpenShift Developer Tools and Services for OCP 4.11jenkins-2-plugins-0:4.11.1683009941-1.el8RHSA-2023:3198
Red Hat OpenShift Container Platform 4.10jenkins-2-plugins-0:4.10.1675144701-1.el8RHSA-2023:0560
Red Hat OpenShift Container Platform 4.9jenkins-2-plugins-0:4.9.1675668922-1.el8RHSA-2023:0777

Frequently Asked Questions

Jenkins Pipeline: Stage View Plugin provides a visualization of Pipeline builds. It also allows users to interact with `input` steps from Pipeline: Input Step Plugin. Pipeline: Stage View Plugin 2.26 and earlier does not correctly encode the ID of `input` steps when using it to generate URLs to proceed or abort Pipeline builds. This allows attackers able to configure Pipelines to specify `input` step IDs resulting in URLs that would bypass the CSRF protection of any target URL in Jenkins. Pipeline: Stage View Plugin 2.27 correctly encodes the ID of `input` steps when using it to generate UR
O3 Security · Impact-Aware SCA

Is CVE-2022-43408 in your dependencies?

Find it across Maven, including transitive dependencies.

Scan my dependencies How O3 SCA works
CVE-2022-43408: pipeline-stage-view CSRF — Fixed in 2.27