CVE-2011-0096

HIGHNVD 6.17.0
EchelonGraph scoreHIGH confidence

“▲” beside the score: it is higher than NVD's CVSS score.

Score elevated to 7.0 because EPSS predicted 47% probability of exploitation within the next 30 days (98th percentile of EPSS-scored CVEs) when EchelonGraph scored this CVE. NVD baseline CVSS 6.1 retained for reference. Confidence: see factors.

Triggered by: EPSS exploit prediction (continuous uplift above 30%)
Sources: EPSS, GitHub Security Advisory, NVD CVSS v3
Weaponized
7.0EG
EchelonGraph verdictPlan mitigationRemediate within your standard update timelines (the SSVC decision on this page).
  • Public exploit code is available (Exploit-DB, marked verified by Exploit-DB)
CISA-KEV: Not listedEPSS PROB: 47%CVSS: 6.1Exploit: Exploit-DB (verified)Exposed services: Not assessed

No fix has been recorded since the CVE record was published in 2011 — use a compensating control (WAF / firewall / segmentation) and check the vendor's advisory.

The MHTML protocol handler in Microsoft Windows XP SP2 and SP3, Windows Server 2003 SP2, Windows Vista SP1 and SP2, Windows Server 2008 Gold, SP2, R2, and R2 SP1, and Windows 7 Gold and SP1 does not properly handle a MIME format in a request for content blocks in a document, which allows remote attackers to conduct cross-site scripting (XSS) attacks via a crafted web site that is visited in Internet Explorer, aka "MHTML Mime-Formatted Request Vulnerability."

CVSS v3
6.1
EG Score
7.0HIGHhigh confidence
EG Risk
57
EG Risk 57/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)
Severity70% × 45%
The EG Score, 7.0 of 10.
Exploitation65% × 40%
EchelonGraph's fixed weight for EG-KEV Tier 2 (Weaponized): 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 public PoC (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (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 2011. Restrict network exposure of the affected system or apply the vendor's mitigation within your standard update timelines, and check the vendor's advisory for a fix.
EPSS PROB
47%
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 2011. Restrict network exposure of the affected system or apply the vendor's mitigation within your standard update timelines, and check the vendor's advisory for a fix.

Exploitation public PoC (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (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)60 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 partial (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 31, 2011

Last Modified

April 29, 2026

Advisory Details (8)

Auto-updated May 29, 2026
No fix on record since 2011. Sources: cert.
Web page
http://www.securitytracker.com/id?1025003
Web page
http://www.securityfocus.com/bid/46055
CERT

VU#326549 - Microsoft Windows MHTML script injection vulnerability

http://www.kb.cert.org/vuls/id/326549
Web page

Microsoft Internet Explorer - MHTML Protocol Handler Cross-Site Scripting - Windows local Exploit

http://www.exploit-db.com/exploits/16071
Web page

www.80vul.com is For Sale

http://www.80vul.com/webzine_0x05/0x05%20IE%E4%B8%8BMHTML%E5%8D%8F%E8%AE%AE%E5%B8%A6%E6%9D%A5%E7%9A%84%E8%B7%A8%E5%9F%9F%E5%8D%B1%E5%AE%B3.html
Web page

About Secunia Research | Flexera

http://secunia.com/advisories/43093
Web page

Archived MSDN and TechNet Blogs | Microsoft Learn

http://blogs.technet.com/b/srd/archive/2011/01/28/more-information-about-the-mhtml-script-injection-vulnerability.aspx
Web page

Archived MSDN and TechNet Blogs | Microsoft Learn

http://blogs.technet.com/b/msrc/archive/2011/01/28/microsoft-releases-security-advisory-2501696.aspx

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 7× in last 7d / 17× 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 75 of 81 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. 25 repeat rows among the latest 100 are merged into the row they repeat. The 6 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

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

Publicly available exploits

(1 reference)

Public exploit code is referenced for this CVE (1 Exploit-DB entry). No fix has been recorded since the CVE record was published in 2011. If the vendor still supports the product, apply the fixed version it names; if it no longer does, isolate the affected system.

  • Exploit-DBEDB-16071✓ verified
    Published Jan 29, 2011

    Microsoft Internet Explorer - MHTML Protocol Handler Cross-Site Scripting

    Open source ↗

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2011-0096?
CVE-2011-0096 is a high-severity vulnerability; its CVE record was published on January 31, 2011. The MHTML protocol handler in Microsoft Windows XP SP2 and SP3, Windows Server 2003 SP2, Windows Vista SP1 and SP2, Windows Server 2008 Gold, SP2, R2, and R2 SP1, and Windows 7 Gold and SP1 does not properly handle a MIME format in a request for content blocks in a document, which allows remote…
When was CVE-2011-0096 made public?
CVE-2011-0096 was made public on January 28, 2011: 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 31, 2011. 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-2011-0096 actively exploited?
CVE-2011-0096 is not currently on CISA's Known Exploited Vulnerabilities catalog. EchelonGraph's EG-KEV model places it in Tier 2 (Weaponized), which is not evidence of exploitation: Exploit-DB marks a public exploit for it as verified. EchelonGraph does not test whether exploit code works. FIRST EPSS estimates a 47% probability of exploitation in the next 30 days (98th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2011-0096?
CVE-2011-0096 has a CVSS v3 base score of 6.1 (NVD). EchelonGraph synthesises NVD + CISA KEV + FIRST EPSS + GHSA into a combined EG score of 7.0 (HIGH).
How do I remediate CVE-2011-0096?
No fix for CVE-2011-0096 has been recorded since its CVE record was published in 2011. Restrict network exposure of the affected system or apply the vendor's mitigation — for example, keep it off the internet or limit it to trusted networks — and check the vendor's advisory for a fix.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2011-0096

Explore →

Is Your Infrastructure Affected by CVE-2011-0096?

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

Book a Demo →Browse All CVEs