GHSA-jmxr-w2jc-qp7w is a high-severity (CVSS 8) Cross-site Scripting (XSS) vulnerability in org.jenkins-ci.plugins:promoted-builds. A fix is available for org.jenkins-ci.plugins:promoted-builds — see the affected versions and patch details below.
Promotion names in Jenkins promoted builds Plugin are not validated when using Job DSL
EPSS Exploitation Probability
EPSS (Exploit Prediction Scoring System) is a daily probability model maintained by FIRST.org. It estimates the likelihood a CVE will be exploited in production environments within the next 30 days, derived from real-world threat intelligence signals.
How urgent is this, really
GHSA-jmxr-w2jc-qp7w plotted by exploitation likelihood (EPSS) against impact (CVSS). The shaded corner — EPSS 50%+ and CVSS 7.0+ — is where this CVE doesn't sit, though severity or exploitability alone can still warrant action.
Where this sits among everything scored
Of 378,156 CVEs with a current EPSS score, this one falls in the < 10% band (highlighted). Real counts from FIRST.org, not a sample — log-scaled since the landscape is heavily right-skewed.
Real-World Exposure
org.jenkins-ci.plugins:promoted-builds☕org.jenkins-ci.plugins:promoted-buildsReal-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 promoted builds Plugin provides dedicated support for defining promotions using Job DSL Plugin.
promoted builds Plugin 873.v6149db_d64130 and earlier does not validate the names of promotions defined in Job DSL. This allows attackers with Job/Configure permission to create a promotion with an unsafe name. As a result, the promotion name could be used for cross-site scripting (XSS) or to replace other config.xml files.
promoted builds Plugin 876.v99d29788b_36b_ and 3.10.1 validates the name of promotions.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| ☕Maven | org.jenkins-ci.plugins:promoted-builds | all versions | 3.10.1org.jenkins-ci.plugins:promoted-builds:3.10.1 |
| ☕Maven | org.jenkins-ci.plugins:promoted-builds | ≥ 3.11&&< 876.v99d29788b | 876.v99d29788borg.jenkins-ci.plugins:promoted-builds:876.v99d29788b |
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for org.jenkins-ci.plugins:promoted-builds, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update org.jenkins-ci.plugins:promoted-builds to 3.10.1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-jmxr-w2jc-qp7w is resolved across your whole dependency graph.
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.
How O3 protects you
O3 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like GHSA-jmxr-w2jc-qp7w can be triaged on real exposure rather than presence alone.
Tailored to GHSA-jmxr-w2jc-qp7w. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.
Frequently Asked Questions
Is GHSA-jmxr-w2jc-qp7w in your dependencies?
O3 Security finds GHSA-jmxr-w2jc-qp7w across Maven dependencies, including transitive ones, and its impact-aware SCA ranks findings by whether your code actually calls the vulnerable path.