CVE-2014-125087 is a critical-severity (CVSS 9.8) XML External Entity (XXE) vulnerability in com.jamesmurty.utils:java-xmlbuilder. 1 public exploit or proof-of-concept reference is indexed, so weaponization risk is real. A fix is available for com.jamesmurty.utils:java-xmlbuilder — see the affected versions and patch details below.
java-xmlbuilder vulnerable to XML External Entity Reference
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.jamesmurty.utils:java-xmlbuilderReal-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
A vulnerability was found in java-xmlbuilder up to 1.1. It has been rated as problematic. Affected by this issue is some unknown functionality. The manipulation leads to xml external entity reference. Upgrading to version 1.2 is able to address this issue. The name of the patch is e6fddca201790abab4f2c274341c0bb8835c3e73. It is recommended to upgrade the affected component. The identifier of this vulnerability is VDB-221480.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| ☕Maven | com.jamesmurty.utils:java-xmlbuilder | all versions | 1.2com.jamesmurty.utils:java-xmlbuilder:1.2 |
Affected Products
java-xmlbuilderjava-xmlbuilder_projectResearch use only. For defensive security, authorized penetration testing, and academic research only. Never execute exploit code against systems without explicit written authorization.
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for com.jamesmurty.utils:java-xmlbuilder, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update com.jamesmurty.utils:java-xmlbuilder to 1.2 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2014-125087 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-2014-125087 in your dependencies?
Find it across Maven, including transitive dependencies.