How severe is CVE-2013-6429?

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

Which packages are affected by CVE-2013-6429?

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

How do I fix CVE-2013-6429?

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

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

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

How do I mitigate CVE-2013-6429 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-6429 actively exploited in the wild?

No public exploit code has been indexed for CVE-2013-6429 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-6429?

CVE-2013-6429 has an EPSS (Exploit Prediction Scoring System) score of 90.6%, placing it in the 100th 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. A score above 50% indicates significantly elevated exploitation risk — immediate patching is strongly recommended.

What type of vulnerability is CVE-2013-6429?

CVE-2013-6429 is classified as Cross-Site Request Forgery (CSRF) (CWE-352), XML External Entity (XXE) (CWE-611). These weakness types describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

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

CVE-2013-6429 was published on January 26, 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-6429 — spring-web

Fix: spring-projects/spring-framework@2ae6a6a

CVE-2013-6429 is a Cross-Site Request Forgery (CSRF) vulnerability in org.springframework:spring-web. EPSS puts its 30-day exploitation probability at 90.6% (100th percentile). A fix is available for org.springframework:spring-web — see the affected versions and patch details below.

Cross-Site Request Forgery in Spring Framework

Also known asGHSA-g6hf-f9cq-q7w7

Published

Jan 26, 2014

Updated

Apr 16, 2026

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

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

EPSS Exploitation Probability

via FIRST.org ↗

90.6%probability of exploitation in next 30 days

Very High Risk0.00%

Lower risk than most CVEs100th percentile — riskier than 100% 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-web

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 SourceHttpMessageConverter in Spring MVC in Spring Framework before 3.2.5 and 4.0.0.M1 through 4.0.0.RC1 does not disable external entity resolution, which allows remote attackers to read arbitrary files, cause a denial of service, and conduct CSRF attacks via crafted XML, aka an XML External Entity (XXE) issue, and a different vulnerability than CVE-2013-4152 and CVE-2013-7315.

Affected Packages

1 total 1 fixed

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

Affected Products

2 products · 4 configurations

Application

spring frameworkpivotal_software

≥ 3.0.0 && ≤ 3.2.4

range

Application

spring frameworkvmware

1 version

4.0.0

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-web, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update org.springframework:spring-web to 3.2.5.RELEASE or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2013-6429 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

RHSA-2014:0401Red Hat JBoss A-MQ 6.1 RHSA-2014:0400Red Hat JBoss Fuse 6.1

Frequently Asked Questions

O3 Security · Impact-Aware SCA

Is CVE-2013-6429 in your dependencies?

Find it across Maven, including transitive dependencies.

Scan my dependencies How O3 SCA works