CVE-2023-41933 is a high-severity (CVSS 8.8) XML External Entity (XXE) vulnerability in org.jenkins-ci.plugins:jobConfigHistory. A fix is available for org.jenkins-ci.plugins:jobConfigHistory — see the affected versions and patch details below.
Job Configuration History Plugin's path traversal allows exploiting XXE vulnerability
Exploitation Status
No confirmed exploitation observed yet
- A successful exploit gives an attacker total control of the affected component, not partial access.
- 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-41933.
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:jobConfigHistoryReal-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 Job Configuration History Plugin 1227.v7a_79fc4dc01f and earlier does not configure its XML parser to prevent XML external entity (XXE) attacks.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| ☕Maven | org.jenkins-ci.plugins:jobConfigHistory | all versions | 1229.v3039470161a_dorg.jenkins-ci.plugins:jobConfigHistory:1229.v3039470161a_d |
Affected Products
job configuration historyjenkinsDetection & 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:jobConfigHistory, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update org.jenkins-ci.plugins:jobConfigHistory to 1229.v3039470161a_d or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2023-41933 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.
Frequently Asked Questions
Is CVE-2023-41933 in your dependencies?
Find it across Maven, including transitive dependencies.