CVE-2023-46650 is a medium-severity (CVSS 5.4) Cross-site Scripting (XSS) vulnerability in com.coravy.hudson.plugins.github:github. A fix is available for com.coravy.hudson.plugins.github:github — see the affected versions and patch details below.
Stored XSS vulnerability in Jenkins GitHub 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-2023-46650.
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.coravy.hudson.plugins.github:githubReal-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 GitHub Plugin 1.37.3 and earlier does not escape the GitHub project URL on the build page when showing changes.
This results in a stored cross-site scripting (XSS) vulnerability exploitable by attackers with Item/Configure permission.
GitHub Plugin 1.37.3.1 escapes GitHub project URL on the build page when showing changes.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| ☕Maven | com.coravy.hudson.plugins.github:github | all versions | 1.37.3.1com.coravy.hudson.plugins.github:github:1.37.3.1 |
Affected Products
githubjenkinsDetection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for com.coravy.hudson.plugins.github:github, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update com.coravy.hudson.plugins.github:github to 1.37.3.1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2023-46650 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-2023-46650 in your dependencies?
Find it across Maven, including transitive dependencies.