How severe is GHSA-vp63-rrcm-9mph?

No CVSS score has been assigned to GHSA-vp63-rrcm-9mph yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-vp63-rrcm-9mph?

GHSA-vp63-rrcm-9mph affects the following packages: org.springframework:spring-oxm (Maven). Ecosystems affected: Maven.

How do I fix GHSA-vp63-rrcm-9mph?

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 GHSA-vp63-rrcm-9mph is resolved across your whole dependency graph.

How do I detect GHSA-vp63-rrcm-9mph 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 GHSA-vp63-rrcm-9mph 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 GHSA-vp63-rrcm-9mph actively exploited in the wild?

Yes. There are 1 known exploit references for GHSA-vp63-rrcm-9mph, 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 GHSA-vp63-rrcm-9mph?

GHSA-vp63-rrcm-9mph has an EPSS (Exploit Prediction Scoring System) score of 5.1%, placing it in the 92th 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 indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

What type of vulnerability is GHSA-vp63-rrcm-9mph?

GHSA-vp63-rrcm-9mph 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 GHSA-vp63-rrcm-9mph published, and has it been updated?

GHSA-vp63-rrcm-9mph was published on May 13, 2022 and was last updated on December 4, 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

Missing XML Validation in Spring FrameworkGHSA-vp63-rrcm-9mph

Fix: spring-projects/spring-framework@434735f

GHSA-vp63-rrcm-9mph 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.

Also known asCVE-2013-7315

Published

May 13, 2022

Updated

Dec 4, 2024

Affected

1 pkg

Patched

1 / 1

Exploits

1 known

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

EPSS Exploitation Probability

via FIRST.org ↗

5.1%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs92th percentile — riskier than 92% 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 MVC in Spring Framework before 3.2.4 and 4.0.0.M1 through 4.0.0.M2 does not disable external entity resolution for the StAX XMLInputFactory, which allows context-dependent attackers to read arbitrary files, cause a denial of service, and conduct CSRF attacks via crafted XML with JAXB, aka an XML External Entity (XXE) issue, and a different vulnerability than CVE-2013-4152. NOTE: this issue was SPLIT from CVE-2013-4152 due to different affected versions.

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 · 28 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 MVC in Spring Framework before 3.2.4 and 4.0.0.M1 through 4.0…

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 GHSA-vp63-rrcm-9mph 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.