How severe is CVE-2013-4002?

No CVSS score has been assigned to CVE-2013-4002 yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by CVE-2013-4002?

CVE-2013-4002 affects the following packages: xerces:xercesImpl (Maven). Ecosystems affected: Maven.

How do I fix CVE-2013-4002?

Update xerces:xercesImpl to 2.12.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2013-4002 is resolved across your whole dependency graph.

How do I detect CVE-2013-4002 in my Maven dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for xerces:xercesImpl, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate CVE-2013-4002 if there is no patch (or I can't update yet)?

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.

How does O3 Security protect against CVE-2013-4002?

O3 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like CVE-2013-4002 can be triaged on real exposure rather than presence alone.

Is CVE-2013-4002 actively exploited in the wild?

No public exploit code has been indexed for CVE-2013-4002 yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

What is the EPSS score for CVE-2013-4002?

CVE-2013-4002 has an EPSS (Exploit Prediction Scoring System) score of 24.7%, placing it in the 98th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score warrants monitoring and prompt remediation.

When was CVE-2013-4002 published, and has it been updated?

CVE-2013-4002 was published on May 13, 2022 and was last updated on December 3, 2024. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

☕ Maven

Not in CISA KEV

CVE-2013-4002 — xercesImpl

Fix: apache/xerces2-j@266e837

CVE-2013-4002 is a security vulnerability in xerces:xercesImpl. EPSS puts its 30-day exploitation probability at 24.7% (98th percentile). A fix is available for xerces:xercesImpl — see the affected versions and patch details below.

Missing XML Validation in Apache Xerces2

Published

May 13, 2022

Updated

Dec 3, 2024

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

Exploitation data as of Sep 21, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

EPSS Exploitation Probability

via FIRST.org ↗

24.7%probability of exploitation in next 30 days

Moderate Risk0.00%

Lower risk than most CVEs98th percentile — riskier than 98% of all scored CVEsHighest risk

EPSS (Exploit Prediction Scoring System) is a daily probability model maintained by FIRST.org. It estimates the likelihood a CVE will be exploited in production environments within the next 30 days, derived from real-world threat intelligence signals.

Real-World Exposure

1 pkg affected

☕xerces:xercesImpl

Real-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

XMLscanner.java in Apache Xerces2 Java Parser before 2.12.0, as used in the Java Runtime Environment (JRE) in IBM Java 5.0 before 5.0 SR16-FP3, 6 before 6 SR14, 6.0.1 before 6.0.1 SR6, and 7 before 7 SR5 as well as Oracle Java SE 7u40 and earlier, Java SE 6u60 and earlier, Java SE 5.0u51 and earlier, JRockit R28.2.8 and earlier, JRockit R27.7.6 and earlier, Java SE Embedded 7u40 and earlier, and possibly other products allows remote attackers to cause a denial of service via vectors related to XML attribute names.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
☕Maven	`xerces:xercesImpl`	all versions	2.12.0`xerces:xercesImpl:2.12.0`

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for xerces:xercesImpl, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update xerces:xercesImpl to 2.12.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2013-4002 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.
How O3 protects you
O3 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like CVE-2013-4002 can be triaged on real exposure rather than presence alone.

Tailored to CVE-2013-4002. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Fixing This On Your OS

If you run this on a Linux distribution, patch through your package manager against the distro's own security advisory below — it tracks the exact backported fix for your release, which can ship on a different timeline (and sometimes a different severity) than the upstream project.

Red HatModerate

Fuse ESB Enterprise is now in Maintenance Support phase receiving only qualified Important and Critical impact security fixes. This issue has been rated as having Moderate security impact and is not currently planned to be addressed in future updates. For additional information, refer to the Fuse Product Life Cycle:…

Product	Fixed in	Advisory
Oracle Java for Red Hat Enterprise Linux 5	`java-1.6.0-sun-1:1.6.0.75-1jpp.3.el5_10`	RHSA-2014:0414
Red Hat Enterprise Linux 5	`java-1.7.0-openjdk-1:1.7.0.45-2.4.3.1.el5_10`	RHSA-2013:1447
Red Hat Enterprise Linux 5	`java-1.6.0-openjdk-1:1.6.0.0-1.42.1.11.14.el5_10`	RHSA-2013:1505
Red Hat Enterprise Linux 6	`java-1.7.0-openjdk-1:1.7.0.45-2.4.3.2.el6_4`	RHSA-2013:1451
Red Hat Enterprise Linux 6	`xerces-j2-0:2.7.1-12.7.el6_5`	RHSA-2014:1319
Red Hat JBoss BPMS 6.0	`xerces-j2`	RHSA-2015:0234
Red Hat JBoss BRMS 6.0	`xerces-j2`	RHSA-2015:0235
Red Hat JBoss Data Grid 6.4	`xerces-j2`	RHSA-2015:0773

Frequently Asked Questions

O3 Security · Impact-Aware SCA

Is CVE-2013-4002 in your dependencies?

O3 Security finds CVE-2013-4002 across Maven dependencies, including transitive ones, and its impact-aware SCA ranks findings by whether your code actually calls the vulnerable path.

Scan my dependencies How O3 SCA works