CVE-2013-0006

HIGHNVD 8.88.8
EchelonGraph scoreMEDIUM confidence

“—” beside the score: it is equal to NVD's CVSS score.

Score 8.8 from GitHub Security Advisory (severity: HIGH) published 2022-05-05. NVD baseline CVSS 8.8; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: EPSS, GitHub Security Advisory, NVD CVSS v3
Elevated
8.8EG
EchelonGraph verdictPlan mitigationRemediate within your standard update timelines (the SSVC decision on this page).
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 28%CVSS: 8.8Exploit: No code on recordExposed services: Not assessed

No fix has been recorded since the CVE record was published in 2013 — if the vendor still supports the product, apply the fixed version it names; if not, isolate the affected system (restrict network access to it, for example with a firewall, or keep it off the internet) or retire the product.

Microsoft XML Core Services (aka MSXML) 3.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 Integer Truncation Vulnerability."

CVSS v3
8.8
EG Score
8.8HIGHmedium confidence
EG Risk
56
EG Risk 56/100

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed (value × EchelonGraph’s weight)
Severity88% × 45%
The EG Score, 8.8 of 10.
Exploitation40% × 40%
EchelonGraph's fixed weight for EG-KEV Tier 3 (Elevated): a constant, not a probability.
Automatability0% × 15%
CISA's SSVC Automatable value: no (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Track* at high (mission-essential systems).
Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.
Action: No fix has been recorded since the CVE record was published in 2013. If the vendor still supports the product, apply the fixed version it names within your standard update timelines; if it no longer does, isolate the affected system (restrict network access to it, for example with a firewall, or keep it off the internet) or retire the product.
EPSS PROB
28%
EPSS %ILE
98th
KEV
Not listed

SSVC (CISA's decision table, applied by EchelonGraph)Track at low or medium mission impact; Track* at high (mission-essential systems).

No fix has been recorded since the CVE record was published in 2013. If the vendor still supports the product, apply the fixed version it names within your standard update timelines; if it no longer does, isolate the affected system (restrict network access to it, for example with a firewall, or keep it off the internet) or retire the product.

Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table

BOD 26-04 (CISA's remediation timeline, Table 1)14 days if the affected system is publicly exposed; Fix on system upgrade if it is not.

In CISA KEV no (CISA's KEV catalog) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

Published

January 9, 2013

Last Modified

April 29, 2026

Advisory Details (2)

Auto-updated Apr 30, 2026
No fix on record since 2013. Sources: cisa.
CISA

OSIsoft PI Interface for OPC XML-DA | CISA

https://us-cert.cisa.gov/ics/advisories/icsa-20-315-01
Web page

Microsoft Security Bulletin MS13-002 - Critical | Microsoft Learn

https://docs.microsoft.com/en-us/security-updates/securitybulletins/2013/ms13-002

Data Freshness Timeline

(refreshed 8× in last 7d / 16× in last 30d)

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). Most recent first.

Showing the most recent 84 of 97 refreshes on record for this CVE.

A repeat, a row identical to one the same pipeline wrote less than 10 seconds earlier, is not a separate refresh and is not counted. 16 repeat rows among the latest 100 are merged into the row they repeat. The 13 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

  1. 2026-10-12 01:34 UTCEG score recompute
  2. 2026-10-11 13:39 UTCEPSS rescoreEPSS 28% · 98th percentile
  3. 2026-10-10 19:54 UTCEPSS rescoreEPSS 28% · 98th percentile
  4. 2026-10-09 20:00 UTCEPSS rescoreEPSS 28% · 98th percentile
  5. 2026-10-08 16:34 UTCEPSS rescoreEPSS 28% · 98th percentile
  6. 2026-10-07 23:39 UTCEPSS rescoreEPSS 28% · 98th percentile
  7. 2026-10-06 15:10 UTCEPSS rescoreEPSS 28% · 98th percentile
  8. 2026-10-05 17:38 UTCEPSS rescoreEPSS 28% · 98th percentile
  9. 2026-09-30 14:58 UTCEPSS rescoreEPSS 28% · 98th percentile
  10. 2026-09-29 08:34 UTCEG score recompute
  11. 2026-09-27 13:39 UTCEPSS rescoreEPSS 28% · 98th percentile
  12. 2026-09-26 15:52 UTCEPSS rescoreEPSS 28% · 98th percentile
  13. 2026-09-24 13:57 UTCEPSS rescoreEPSS 28% · 98th percentile
  14. 2026-09-18 19:21 UTCEPSS rescoreEPSS 28% · 98th percentile
  15. 2026-09-15 03:04 UTCEPSS rescoreEPSS 28% · 97th percentile
  16. 2026-09-12 14:55 UTCEPSS rescoreEPSS 28% · 97th percentile
  17. 2026-09-11 09:30 UTCEPSS rescoreEPSS 28% · 97th percentile
  18. 2026-09-06 13:42 UTCEPSS rescoreEPSS 28% · 97th percentile
  19. 2026-09-05 15:22 UTCEPSS rescoreEPSS 28% · 98th percentile
  20. 2026-09-04 13:55 UTCEPSS rescoreEPSS 28% · 97th percentile
  21. 2026-09-02 14:06 UTCEPSS rescoreEPSS 28% · 97th percentile
  22. 2026-09-01 13:47 UTCEPSS rescoreEPSS 28% · 97th percentile
  23. 2026-08-27 14:20 UTCEPSS rescoreEPSS 28% · 97th percentile
  24. 2026-08-26 14:40 UTCEPSS rescoreEPSS 28% · 97th percentile
  25. 2026-08-25 13:43 UTCEPSS rescoreEPSS 28% · 97th percentile
Show 59 more
  1. 2026-08-24 07:23 UTCEPSS rescoreEPSS 28% · 98th percentile
  2. 2026-08-21 23:44 UTCEPSS rescoreEPSS 28% · 97th percentile
  3. 2026-08-20 22:50 UTCEPSS rescoreEPSS 28% · 97th percentile
  4. 2026-08-19 16:59 UTCEPSS rescoreEPSS 28% · 97th percentile
  5. 2026-08-18 13:42 UTCEPSS rescoreEPSS 28% · 97th percentile
  6. 2026-08-16 02:09 UTCEPSS rescoreEPSS 28% · 97th percentile
  7. 2026-08-15 01:25 UTCEPSS rescoreEPSS 28% · 97th percentile
  8. 2026-08-12 13:45 UTCEPSS rescoreEPSS 28% · 97th percentile
  9. 2026-08-08 16:31 UTCEPSS rescoreEPSS 28% · 97th percentile
  10. 2026-08-07 16:21 UTCEPSS rescoreEPSS 28% · 97th percentile
  11. 2026-08-06 13:42 UTCEPSS rescoreEPSS 28% · 97th percentile
  12. 2026-08-05 19:12 UTCEPSS rescoreEPSS 28% · 97th percentile
  13. 2026-07-28 15:31 UTCEPSS rescoreEPSS 28% · 97th percentile
  14. 2026-07-25 14:12 UTCEPSS rescoreEPSS 28% · 97th percentile
  15. 2026-07-23 14:14 UTCEPSS rescoreEPSS 28% · 97th percentile
  16. 2026-07-23 01:09 UTCEG score recompute
  17. 2026-07-23 00:12 UTCEG score recompute
  18. 2026-07-22 21:50 UTCEG score recompute
  19. 2026-07-22 14:04 UTCEPSS rescoreEPSS 28% · 97th percentile
  20. 2026-07-21 15:21 UTCEPSS rescoreEPSS 28% · 97th percentile
  21. 2026-07-20 17:03 UTCEPSS rescoreEPSS 28% · 97th percentile
  22. 2026-07-19 02:25 UTCEPSS rescoreEPSS 28% · 97th percentile
  23. 2026-07-18 10:00 UTCEPSS rescoreEPSS 28% · 97th percentile
  24. 2026-07-16 16:58 UTCEPSS rescoreEPSS 28% · 97th percentile
  25. 2026-07-15 16:54 UTCEPSS rescoreEPSS 28% · 97th percentile
  26. 2026-07-15 01:56 UTCEPSS rescoreEPSS 28% · 97th percentile
  27. 2026-07-13 22:26 UTCEPSS rescoreEPSS 28% · 97th percentile
  28. 2026-07-13 06:08 UTCEPSS rescoreEPSS 28% · 97th percentile
  29. 2026-07-11 08:23 UTCEPSS rescoreEPSS 28% · 97th percentile
  30. 2026-07-09 19:05 UTCEPSS rescoreEPSS 28% · 97th percentile
  31. 2026-07-08 15:10 UTCEPSS rescoreEPSS 28% · 97th percentile
  32. 2026-07-05 02:26 UTCEPSS rescoreEPSS 28% · 97th percentile
  33. 2026-07-01 15:02 UTCEPSS rescoreEPSS 28% · 97th percentile
  34. 2026-06-29 14:02 UTCEPSS rescoreEPSS 28% · 97th percentile
  35. 2026-06-28 04:53 UTCEPSS rescoreEPSS 28% · 97th percentile
  36. 2026-06-27 03:05 UTCEPSS rescoreEPSS 28% · 97th percentile
  37. 2026-06-25 13:46 UTCEPSS rescoreEPSS 28% · 97th percentile
  38. 2026-06-24 14:02 UTCEPSS rescoreEPSS 28% · 97th percentile
  39. 2026-06-23 21:30 UTCEPSS rescoreEPSS 28% · 97th percentile
  40. 2026-06-22 14:22 UTCEPSS rescoreEPSS 28% · 97th percentile
  41. 2026-06-21 14:53 UTCEPSS rescoreEPSS 28% · 97th percentile
  42. 2026-06-21 01:56 UTCEPSS rescoreEPSS 28% · 97th percentile
  43. 2026-06-18 17:49 UTCEPSS rescoreEPSS 28% · 97th percentile
  44. 2026-06-17 17:49 UTCEPSS rescoreEPSS 28% · 97th percentile
  45. 2026-06-16 17:49 UTCEPSS rescoreEPSS 27% · 97th percentile
  46. 2026-06-15 17:44 UTCEPSS rescoreEPSS 27% · 97th percentile
  47. 2026-06-14 23:14 UTCEPSS rescoreEPSS 68% · 98th percentile
  48. 2026-06-13 22:57 UTCEPSS rescoreEPSS 68% · 98th percentile
  49. 2026-06-12 23:08 UTCEPSS rescoreEPSS 68% · 98th percentile
  50. 2026-06-11 13:56 UTCEPSS rescoreEPSS 68% · 98th percentile
  51. 2026-06-10 13:18 UTCEPSS rescoreEPSS 68% · 98th percentile
  52. 2026-06-08 14:14 UTCEPSS rescoreEPSS 68% · 98th percentile
  53. 2026-06-05 22:44 UTCEPSS rescoreEPSS 68% · 98th percentile
  54. 2026-06-05 06:08 UTCEPSS rescoreEPSS 68% · 98th percentile
  55. 2026-06-02 20:10 UTCEPSS rescoreEPSS 68% · 98th percentile
  56. 2026-06-01 13:49 UTCEPSS rescoreEPSS 68% · 98th percentile
  57. 2026-05-31 00:14 UTCEPSS rescoreEPSS 68% · 98th percentile
  58. 2026-05-29 01:25 UTCEG score recompute
  59. 2026-05-29 01:25 UTCGHSA enrichmentGHSA-4jcp-w4pp-vm92 · GitHub severity HIGH · GitHub CVSS 8.8

Frequently asked(5)

What is CVE-2013-0006?
CVE-2013-0006 is a high-severity vulnerability; its CVE record was published on January 9, 2013. Microsoft XML Core Services (aka MSXML) 3.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 Integer Truncation Vulnerability."
When was CVE-2013-0006 made public?
CVE-2013-0006 was made public on January 8, 2013: that is the date its CVE record's CNA, Microsoft Corporation, gives for when the vulnerability was made public. The CVE record itself was published on January 9, 2013. EchelonGraph's copy of the record carries a last-modified date of April 29, 2026; the record at its source may have been updated since.
Is CVE-2013-0006 actively exploited?
CVE-2013-0006 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 28% probability of exploitation in the next 30 days (98th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2013-0006?
CVE-2013-0006 has a CVSS v3 base score of 8.8 (NVD).
How do I remediate CVE-2013-0006?
No fix for CVE-2013-0006 has been recorded since its CVE record was published in 2013. If the vendor still supports the product, apply the fixed version it names; if it no longer does, isolate the affected system (restrict network access to it, for example with a firewall, or keep it off the internet) or retire the product.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2013-0006

Explore →

Is Your Infrastructure Affected by CVE-2013-0006?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Book a Demo →Browse All CVEs