CVE-2011-1252

MEDIUMNVD 6.16.1
EchelonGraph scoreMEDIUM confidence

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

Score 6.1 from GitHub Security Advisory published 2022-05-13. NVD baseline CVSS 6.1; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: EPSS, GitHub Security Advisory, NVD CVSS v3
Elevated
6.1EG
EchelonGraph verdictMonitorRemediate within your standard update timelines (the SSVC decision on this page).
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 14%CVSS: 6.1Exploit: No code on recordExposed services: Not assessed

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 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.

Cross-site scripting (XSS) vulnerability in the SafeHTML function in the toStaticHTML API in Microsoft Internet Explorer 7 and 8, Office SharePoint Server 2007 SP2, Office SharePoint Server 2010 Gold and SP1, Groove Server 2010 Gold and SP1, Windows SharePoint Services 3.0 SP2, and SharePoint Foundation 2010 Gold and SP1 allows remote attackers to inject arbitrary web script or HTML via unspecified strings, aka "toStaticHTML Information Disclosure Vulnerability" or "HTML Sanitization Vulnerability."

CVSS v3
6.1
EG Score
6.1MEDIUMmedium confidence
EG Risk
43
EG Risk 43/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)
Severity61% × 45%
The EG Score, 6.1 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 every mission impact level.
Exploitation none (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. 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
14%
EPSS %ILE
96th
KEV
Not listed

SSVC (CISA's decision table, applied by EchelonGraph)Track at every mission impact level.

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 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 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

June 16, 2011

Last Modified

April 29, 2026

Advisory Details (2)

Auto-updated May 29, 2026
No fix on record since 2011.
Web page

Microsoft Security Bulletin MS11-074 - Important | Microsoft Learn

https://docs.microsoft.com/en-us/security-updates/securitybulletins/2011/ms11-074
Web page

Microsoft Security Bulletin MS11-050 - Critical | Microsoft Learn

https://docs.microsoft.com/en-us/security-updates/securitybulletins/2011/ms11-050

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 8× 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 77 of 107 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. 23 repeat rows among the latest 100 are merged into the row they repeat. The 30 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

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

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2011-1252?
CVE-2011-1252 is a medium-severity vulnerability; its CVE record was published on June 16, 2011. Cross-site scripting (XSS) vulnerability in the SafeHTML function in the toStaticHTML API in Microsoft Internet Explorer 7 and 8, Office SharePoint Server 2007 SP2, Office SharePoint Server 2010 Gold and SP1, Groove Server 2010 Gold and SP1, Windows SharePoint Services 3.0 SP2, and SharePoint…
When was CVE-2011-1252 made public?
CVE-2011-1252 was made public on June 14, 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 June 16, 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-1252 actively exploited?
CVE-2011-1252 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 14% probability of exploitation in the next 30 days (96th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2011-1252?
CVE-2011-1252 has a CVSS v3 base score of 6.1 (NVD).
How do I remediate CVE-2011-1252?
No fix for CVE-2011-1252 has been recorded since its 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 (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-2011-1252

Explore →

Is Your Infrastructure Affected by CVE-2011-1252?

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

Book a Demo →Browse All CVEs