CVE-2013-3893
Microsoft Internet Explorer Resource Management Errors Vulnerability
Microsoft Internet Explorer
Use-after-free vulnerability in the SetMouseCapture implementation in mshtml.dll in Microsoft Internet Explorer 6 through 11 allows remote attackers to execute arbitrary code via crafted JavaScript strings, as demonstrated by use of an ms-help: URL that triggers loading of hxds.dll.
Exploitation status
CISA Known Exploited Vulnerabilities
Listed by CISA on 12 August 2025. US federal agencies were required to remediate it by 2 September 2025.
EPSS — exploitation probability
FIRST puts the probability of exploitation activity in the next 30 days at 87.5%, which is higher than 99.8% of all scored vulnerabilities. EPSS is a forecast of activity, not a measure of severity, and it is rescored daily.
CVSS vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H
Frequently asked questions
Is CVE-2013-3893 being exploited by ransomware groups?
No ransomware group in this database is currently recorded as exploiting CVE-2013-3893.
What does CVE-2013-3893 affect?
CVE-2013-3893 affects Microsoft Internet Explorer. Use-after-free vulnerability in the SetMouseCapture implementation in mshtml.dll in Microsoft Internet Explorer 6 through 11 allows remote attackers to execute arbitrary code via crafted JavaScript strings, as demonstrated by use of an ms-help: URL that triggers loading of hxds.dll.
How severe is CVE-2013-3893?
CVE-2013-3893 is rated HIGH with a CVSS base score of 8.8. EPSS puts the probability of exploitation in the next 30 days at 87.5%, higher than 99.8% of all scored vulnerabilities. It is listed in the CISA Known Exploited Vulnerabilities catalog, with a federal remediation deadline of 2 September 2025.
How should organisations respond to CVE-2013-3893?
Apply the vendor patch for Microsoft Internet Explorer as the first priority, and treat any internet-facing instance as the most urgent. Because this vulnerability is associated with ransomware activity, also review whether the affected systems were reachable before patching, rather than assuming that patching alone closes the incident.