CVE-2013-7315: n/a vulnerability

CVE-2013-7315: The Spring MVC in Spring Framework before 3.2.4 and 4.0.0.M1 through 4.0.0.M2 does not disable external ent...

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.

UnknownCVSS not scoredNot KEV-listedUpdatedAug 6, 2024, 18:01 UTC (UTC+00:00)

Security readout for executives and security teams

This issue affects older Spring MVC applications that process XML through JAXB. A crafted XML request may make the server fetch external entities, which can expose local files, consume resources, or trigger unintended requests. Business urgency depends on whether vulnerable Spring versions are still used on internet-facing or partner-facing XML endpoints. Exposure is most likely in legacy Java web applications using vulnerable Spring MVC versions with XML request handling through JAXB. Risk increases when XML endpoints are reachable by untrusted users. The bundle does not provide CPEs, deployment prevalence, or a complete product inventory mapping. Treat as a legacy exposure cleanup item with high impact if reachable. Prioritize systems that process XML from customers, partners, or unauthenticated users. If no vulnerable Spring versions or XML binding paths exist, business urgency drops substantially. Mitigation focus: Inventory Spring Framework versions in all Java web applications.; Upgrade affected Spring MVC deployments to non-vulnerable supported versions.; Prioritize internet-facing XML endpoints and partner integration APIs..

Prepared: Jun 14, 2026, 14:50 UTC (UTC+00:00)

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cve · low confidence lookup

CVE-2013-7315 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup

Vulnerability profileCVE Program record

Severity: Unknown
CVSS: Not scored
Known Exploited: No
Published: Jan 23, 2014, 21:00 UTC (UTC+00:00)

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

0CVSS vectors

0Timeline events

0ADP providers

2Source links

CVSS and timeline data

No CVSS vectors or timeline events were available in the normalized CVE source material.

Source materials

CVE List V5 sourceCVE List V5
https://jira.springsource.org/browse/SPR-10806CVE reference · x_refsource_CONFIRM

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus

n/an/an/aListed

Weakness

CWE details

No CWE listed

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.