CVE-2013-4152

NONECVSS 0.0Elevated
0.0
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • No confirmed exploitation signals yet
CISA-KEV: Not listedEPSS: 26%CVSS: Exploit: NoneExposed: 0

A fix is available — apply it.

The Spring OXM wrapper in Spring Framework before 3.2.4 and 4.0.0.M1, when using the JAXB marshaller, does not disable entity resolution, which allows context-dependent attackers to read arbitrary files, cause a denial of service, and conduct CSRF attacks via an XML external entity declaration in conjunction with an entity reference in a (1) DOMSource, (2) StAXSource, (3) SAXSource, or (4) StreamSource, aka an XML External Entity (XXE) issue.

CVSS v3
EG Score
0.0(none)
EPSS
97.8%
KEV
Not listed

Published

January 23, 2014

Last Modified

April 29, 2026

Vendor Advisories for CVE-2013-4152(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Patch Availability(4)

Vendor / EcosystemFixed in / PatchReleasedSource
redhatpatch2014-04-14redhat
redhatpatch2014-04-14redhat
redhatactivemq-0:5.9.0-4.redhat.610328.el6op2014-03-05redhat
redhatspring2014-02-25redhat

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(1 across 1 ecosystem)
Maven(1)
PackageVulnerable rangeFixed inDependents
org.springframework:spring-oxm3.0.0.RELEASE ... 3.2.3.RELEASE (17 versions)3.2.4.RELEASE

Additional Vendor Advisories

(4)

Data Freshness Timeline

(refreshed 3× in last 7d / 30× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

  1. 2026-07-05 03:25 UTCOSV refresh
  2. 2026-07-04 06:27 UTCEPSS rescore
  3. 2026-07-01 15:02 UTCEPSS rescore
  4. 2026-06-29 14:02 UTCEPSS rescore
  5. 2026-06-28 14:03 UTCEPSS rescore
  6. 2026-06-28 04:53 UTCEPSS rescore
  7. 2026-06-28 04:53 UTCEPSS rescore
  8. 2026-06-27 03:05 UTCEPSS rescore
  9. 2026-06-25 13:46 UTCEPSS rescore
  10. 2026-06-24 14:02 UTCEPSS rescore
  11. 2026-06-24 14:02 UTCEPSS rescore
  12. 2026-06-23 21:30 UTCEPSS rescore
  13. 2026-06-22 14:22 UTCEPSS rescore
  14. 2026-06-22 14:22 UTCEPSS rescore
  15. 2026-06-21 01:57 UTCEPSS rescore
  16. 2026-06-21 01:56 UTCEPSS rescore
  17. 2026-06-19 19:23 UTCEPSS rescore
  18. 2026-06-19 19:22 UTCEPSS rescore
  19. 2026-06-18 17:49 UTCEPSS rescore
  20. 2026-06-18 17:49 UTCEPSS rescore
  21. 2026-06-17 17:49 UTCEPSS rescore
  22. 2026-06-17 17:49 UTCEPSS rescore
  23. 2026-06-16 17:49 UTCEPSS rescore
  24. 2026-06-16 17:49 UTCEPSS rescore
  25. 2026-06-16 14:44 UTCOSV refresh
Show 37 more
  1. 2026-06-15 17:44 UTCEPSS rescore
  2. 2026-06-12 23:08 UTCEPSS rescore
  3. 2026-06-11 13:56 UTCEPSS rescore
  4. 2026-06-10 13:18 UTCEPSS rescore
  5. 2026-06-08 14:14 UTCEPSS rescore
  6. 2026-06-05 22:44 UTCEPSS rescore
  7. 2026-06-05 22:44 UTCEPSS rescore
  8. 2026-06-05 06:08 UTCEPSS rescore
  9. 2026-06-05 06:08 UTCEPSS rescore
  10. 2026-06-02 20:10 UTCEPSS rescore
  11. 2026-06-02 20:10 UTCEPSS rescore
  12. 2026-06-01 13:49 UTCEPSS rescore
  13. 2026-06-01 13:49 UTCEPSS rescore
  14. 2026-05-31 00:14 UTCEPSS rescore
  15. 2026-05-31 00:14 UTCEPSS rescore
  16. 2026-05-29 13:41 UTCEPSS rescore
  17. 2026-05-29 13:41 UTCEPSS rescore
  18. 2026-05-28 20:39 UTCEG score recompute
  19. 2026-05-28 20:39 UTCVendor advisory
  20. 2026-05-28 13:42 UTCEPSS rescore
  21. 2026-05-28 13:42 UTCEPSS rescore
  22. 2026-05-28 13:42 UTCEPSS rescore
  23. 2026-05-27 13:38 UTCEPSS rescore
  24. 2026-05-27 13:38 UTCEPSS rescore
  25. 2026-05-24 16:43 UTCEPSS rescore
  26. 2026-05-24 09:21 UTCOSV refresh
  27. 2026-05-22 21:15 UTCEPSS rescore
  28. 2026-05-22 21:15 UTCEPSS rescore
  29. 2026-05-22 21:15 UTCEPSS rescore
  30. 2026-05-21 22:39 UTCEPSS rescore
  31. 2026-05-20 22:37 UTCEPSS rescore
  32. 2026-05-20 22:37 UTCEPSS rescore
  33. 2026-05-20 11:21 UTCEPSS rescore
  34. 2026-05-20 11:21 UTCEPSS rescore
  35. 2026-05-20 11:21 UTCEPSS rescore
  36. 2026-05-18 21:29 UTCEPSS rescore
  37. 2026-05-18 21:29 UTCEPSS rescore

Frequently asked(4)

What is CVE-2013-4152?
CVE-2013-4152 is a none vulnerability published on January 23, 2014. The Spring OXM wrapper in Spring Framework before 3.2.4 and 4.0.0.M1, when using the JAXB marshaller, does not disable entity resolution, which allows context-dependent attackers to read arbitrary files, cause a denial of service, and conduct CSRF attacks via an XML external entity declaration in…
When was CVE-2013-4152 disclosed?
CVE-2013-4152 was first published in the National Vulnerability Database on January 23, 2014, with the most recent update on April 29, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2013-4152 actively exploited?
CVE-2013-4152 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 97.8% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
How do I remediate CVE-2013-4152?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2013-4152, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2013-4152

Explore →

Is Your Infrastructure Affected by CVE-2013-4152?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.