CVE-2012-1858 json
The toStaticHTML API (aka the SafeHTML component) in Microsoft Internet Explorer 8 and 9, Communicator 2007 R2, and Lync 2010 and 2010 Atte…
published 2012-06-12 14 y ago modified 2026-06-16 4 mo ago also EUVD-2012-1868
- cvss
- 4.3
- version 2.0, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 22.0%
- EPSS 22.0% chance of exploitation in 30 days, percentile 97%
- public exploits
- 1
- Exploit-DB
Summary
The toStaticHTML API (aka the SafeHTML component) in Microsoft Internet Explorer 8 and 9, Communicator 2007 R2, and Lync 2010 and 2010 Attendee does not properly handle event attributes and script, which makes it easier for remote attackers to conduct cross-site scripting (XSS) attacks via a crafted HTML document, aka "HTML Sanitization Vulnerability."
Timeline
- Published
- First public exploit (EDB-19777)
Exploit prediction
22.02% chance of exploitation in the next 30 days, higher than 97% of all scored CVEs (FIRST EPSS, 2026-11-09).
Exploits and checks
- EDB-19777 Microsoft Internet Explorer 9 / SharePoint / Lync - toStaticHTML HTML Sanitizing Bypass (MS12-037/MS12-039/MS12-050) dos, 2012-07-12
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 2.0 | 4.3 | AV:N/AC:M/Au:N/C:P/I:N/A:N |
Classification
- Weakness
-
- CWE-200 Exposure of Sensitive Information to an Unauthorized Actor
References
-
docs.microsoft.com
/en-us/security-updates/securitybulletins/2012/ms12-050
vendor-advisory
-
docs.microsoft.com
/en-us/security-updates/securitybulletins/2012/ms12-037
vendor-advisory
-
docs.microsoft.com
/en-us/security-updates/securitybulletins/2012/ms12-039
vendor-advisory
-
us-cert.gov
/cas/techalerts/TA12-192A.html
third-party-advisory, us-government-resource
-
us-cert.gov
/cas/techalerts/TA12-164A.html
third-party-advisory, us-government-resource
-
oval.cisecurity.org
/repository/search/definition/oval%3Aorg.mitre.oval%3Adef%3A15530
vdb-entry, signature
Sources
- CVE List CVE-2012-1858
- NVD CVE-2012-1858
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.