CVE-2022-46684 — checkmarx
HIGHCVE-2022-46684 is a high-severity (CVSS 7.5) Cross-site Scripting (XSS) vulnerability in com.checkmarx.jenkins:checkmarx. A fix is available for com.checkmarx.jenkins:checkmarx — see the affected versions and patch details below.
Stored XSS vulnerability in Jenkins Checkmarx Plugin
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-46684.
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
com.checkmarx.jenkins:checkmarxReal-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
heckmarx Plugin processes Checkmarx service API responses and generates HTML reports from them for rendering on the Jenkins UI.
Checkmarx Plugin 2022.3.3 and earlier does not escape values returned from the Checkmarx service API before inserting them into HTML reports. This results in a stored cross-site scripting (XSS) vulnerability.
While Jenkins users without Overall/Administer permission are not allowed to configure the URL to the Checkmarx service, this could still be exploited via man-in-the-middle attacks.
Checkmarx Plugin 2022.4.3 escapes values returned from the Checkmarx service API before inserting them into HTML reports.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| ☕Maven | com.checkmarx.jenkins:checkmarx | all versions | 2022.4.3com.checkmarx.jenkins:checkmarx:2022.4.3 |
Affected Products
checkmarxjenkinsDetection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for com.checkmarx.jenkins:checkmarx, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update com.checkmarx.jenkins:checkmarx to 2022.4.3 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2022-46684 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 CVE-2022-46684 in your dependencies?
Find it across Maven, including transitive dependencies.