Stored XSS vulnerability in Matrix Project PluginGHSA-vqwg-4v6f-h6x5
MEDIUMFix: jenkinsci/matrix-project-plugin@78cc605GHSA-vqwg-4v6f-h6x5 is a medium-severity (CVSS 5.4) Cross-site Scripting (XSS) vulnerability in org.jenkins-ci.plugins:matrix-project. EPSS puts its 30-day exploitation probability at 81.8% (100th percentile). A fix is available for org.jenkins-ci.plugins:matrix-project — see the affected versions and patch details below.
EPSS Exploitation Probability
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
org.jenkins-ci.plugins:matrix-project☕org.jenkins-ci.plugins:matrix-projectReal-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 Matrix Project Plugin prior to 1.20 and 1.18.1 does not escape HTML metacharacters in node and label names, and label descriptions.
This results in a stored cross-site scripting (XSS) vulnerability exploitable by attackers with Agent/Configure permission.
Matrix Project Plugin 1.20 and 1.18.1 escapes HTML metacharacters in node and label names, and label descriptions.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| ☕Maven | org.jenkins-ci.plugins:matrix-project | ≥ 1.19&&< 1.20 | 1.20org.jenkins-ci.plugins:matrix-project:1.20 |
| ☕Maven | org.jenkins-ci.plugins:matrix-project | all versions | 1.18.1org.jenkins-ci.plugins:matrix-project:1.18.1 |
Affected Products
matrix projectjenkinscommunications cloud native core automated test suiteoracleDetection & 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:matrix-project, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update org.jenkins-ci.plugins:matrix-project to 1.20 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-vqwg-4v6f-h6x5 is resolved across your whole dependency graph.
Workarounds
Escape or sanitise the affected output on the server side rather than relying on client-side filtering, and add a Content-Security-Policy that blocks inline script execution so injected markup cannot run even if it reaches the page.
Frequently Asked Questions
Is GHSA-vqwg-4v6f-h6x5 in your dependencies?
Find it across Maven, including transitive dependencies.