How severe is CVE-2013-4152?

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

Which packages are affected by CVE-2013-4152?

CVE-2013-4152 affects the following packages: org.springframework:spring-oxm (Maven). Ecosystems affected: Maven.

How do I fix CVE-2013-4152?

Update org.springframework:spring-oxm to 3.2.4.RELEASE or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2013-4152 is resolved across your whole dependency graph.

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

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

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

Cap what an attacker can consume: apply request size, rate and timeout limits in front of the affected component, and run it with memory and CPU limits so exhaustion degrades one worker rather than the whole service.

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

Yes. There are 1 known exploit references for CVE-2013-4152, including 1 in-the-wild exploitation observed on GitHub and other sources. Treat this as actively exploitable and prioritize patching immediately. All exploit code should only be run in an isolated sandbox environment for research or authorized testing — never against production systems without explicit written authorization.

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

CVE-2013-4152 has an EPSS (Exploit Prediction Scoring System) score of 25.6%, 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.

What type of vulnerability is CVE-2013-4152?

CVE-2013-4152 is classified as CWE-264 (CWE-264). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

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

CVE-2013-4152 was published on January 23, 2014 and was last updated on April 16, 2026. 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-4152 — spring-oxm

Fix: spring-projects/spring-framework#317

CVE-2013-4152 is a CWE-264 vulnerability in org.springframework:spring-oxm. 1 public exploit or proof-of-concept reference is indexed, so weaponization risk is real. A fix is available for org.springframework:spring-oxm — see the affected versions and patch details below.

Cross-Site Request Forgery in Spring Framework

Also known asGHSA-rp4p-g69r-438x

Published

Jan 23, 2014

Updated

Apr 16, 2026

Affected

1 pkg

Patched

1 / 1

Exploits

1 known

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

EPSS Exploitation Probability

via FIRST.org ↗

25.6%probability of exploitation in next 30 days

Moderate Risk0.00%

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

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

Real-World Exposure

1 pkg affected

☕org.springframework:spring-oxm

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

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.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
☕Maven	`org.springframework:spring-oxm`	all versions	3.2.4.RELEASE`org.springframework:spring-oxm:3.2.4.RELEASE`

Affected Products

2 products · 27 configurations

Application

spring frameworkspringsource

8 versions

3.0.03.0.0.m13.0.0.m23.0.13.0.23.0.33.0.43.0.5

Application

spring frameworkvmware

≤ 3.2.3

11 versions

3.0.63.0.73.1.03.1.13.1.23.1.33.1.43.2.03.2.13.2.24.0.0

Exploits & PoCs

Research use only. For defensive security, authorized penetration testing, and academic research only. Never execute exploit code against systems without explicit written authorization.

The Spring OXM wrapper in Spring Framework before 3.2.4 and 4.0.0.M1, wh…

jira.springsource.orgNVDNov 2016

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for org.springframework:spring-oxm, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update org.springframework:spring-oxm to 3.2.4.RELEASE or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2013-4152 is resolved across your whole dependency graph.
Workarounds
Cap what an attacker can consume: apply request size, rate and timeout limits in front of the affected component, and run it with memory and CPU limits so exhaustion degrades one worker rather than the whole service.

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

Product	Fixed in	Advisory
Red Hat JBoss A-MQ 6.1	see advisory	RHSA-2014:0401
Red Hat JBoss Fuse 6.1	see advisory	RHSA-2014:0400
Red Hat JBoss SOA Platform 5.3	`spring`	RHSA-2014:0212
Red Hat OpenShift Enterprise 2.0	`activemq-0:5.9.0-4.redhat.610328.el6op`	RHSA-2014:0245
RHEL 6 Version of OpenShift Enterprise 1.2	`activemq-0:5.9.0-4.redhat.610328.el6op`	RHSA-2014:0254

Frequently Asked Questions

O3 Security · Impact-Aware SCA

Is CVE-2013-4152 in your dependencies?

Find it across Maven, including transitive dependencies.

Scan my dependencies How O3 SCA works