Skip to content
Fencer Intel
medium 4.3

CVE-2010-3324 json

The toStaticHTML function in Microsoft Internet Explorer 8, and the SafeHTML function in Microsoft Windows SharePoint Services 3.0 SP2, Sha…

published 16y ago modified 4mo ago also EUVD-2010-3322

cvss
4.3
version 2.0, NVD
cisa kev
Not listed
not in CISA's catalog
epss
25.0%
EPSS 25.0% chance of exploitation in 30 days, percentile 97%
public exploits
1
Exploit-DB

Summary

The toStaticHTML function in Microsoft Internet Explorer 8, and the SafeHTML function in Microsoft Windows SharePoint Services 3.0 SP2, SharePoint Foundation 2010, Office SharePoint Server 2007 SP2, Groove Server 2010, and Office Web Apps, allows remote attackers to bypass the cross-site scripting (XSS) protection mechanism and conduct XSS attacks via a crafted use of the Cascading Style Sheets (CSS) @import rule, aka "HTML Sanitization Vulnerability," a different vulnerability than CVE-2010-1257.

Is CVE-2010-3324 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 Fencer

Timeline

  1. First public exploit (EDB-34478)
  2. Published

Exploit prediction

25.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-34478 Microsoft Internet Explorer 8 - 'toStaticHTML()' HTML Sanitization Bypass remote, 2010-08-16
  • wooyun.org http://www.wooyun.org/bug.php?action=view&id=189 referenced PoC, tagged "exploit" by a source, unverified
  • archives.neohapsis.com http://archives.neohapsis.com/archives/fulldisclosure/2010-08/0179.html referenced PoC, tagged "exploit" by a source, unverified

CVSS scores

assigned by version score vector
NVD 2.0 4.3 AV:N/AC:M/Au:N/C:N/I:P/A:N

Classification

Weakness
  • CWE-79 Improper Neutralization of Input During Web Page Generation

References

Sources

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.