CVE-2013-0007 in the critical feed json
Microsoft XML Core Services (aka MSXML) 4.0, 5.0, and 6.0 does not properly parse XML content, which allows remote attackers to execute arb…
published 13y ago modified 4mo ago also EUVD-2013-0050
- cvss
- 9.3
- version 2.0, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 31.6%
- EPSS 31.6% chance of exploitation in 30 days, percentile 98%
- public exploits
- 0
- none known
Summary
Microsoft XML Core Services (aka MSXML) 4.0, 5.0, and 6.0 does not properly parse XML content, which allows remote attackers to execute arbitrary code via a crafted web page, aka "MSXML XSLT Vulnerability."
Is CVE-2013-0007 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerExploit prediction
31.57% chance of exploitation in the next 30 days, higher than 98% of all scored CVEs (FIRST EPSS, 2026-11-09).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 2.0 | 9.3 | AV:N/AC:M/Au:N/C:C/I:C/A:C |
Classification
- Weakness
-
- CWE-94 Improper Control of Generation of Code
References
-
docs.microsoft.com
/en-us/security-updates/securitybulletins/2013/ms13-002
vendor-advisory
-
us-cert.gov
/cas/techalerts/TA13-008A.html
third-party-advisory, us-government-resource
-
oval.cisecurity.org
/repository/search/definition/oval%3Aorg.mitre.oval%3Adef%3A15458
vdb-entry, signature
Sources
- CVE List CVE-2013-0007
- NVD CVE-2013-0007
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.