Skip to content
Fencer Intel
critical 9.3

CVE-2010-3973 in the critical feed json

The WMITools ActiveX control in WBEMSingleView.ocx 1.50.1131.0 in Microsoft WMI Administrative Tools 1.1 and earlier in Microsoft Windows X…

published 15y ago modified 4mo ago also EUVD-2010-3950

cvss
9.3
version 2.0, NVD
cisa kev
Not listed
not in CISA's catalog
epss
71.7%
EPSS 71.7% chance of exploitation in 30 days, percentile 99.4%
public exploits
3
Metasploit and Exploit-DB

Summary

The WMITools ActiveX control in WBEMSingleView.ocx 1.50.1131.0 in Microsoft WMI Administrative Tools 1.1 and earlier in Microsoft Windows XP SP2 and SP3 allows remote attackers to execute arbitrary code via a crafted argument to the AddContextRef method, possibly an untrusted pointer dereference, aka "Microsoft WMITools ActiveX Control Vulnerability."

Is CVE-2010-3973 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 (Metasploit exploit/windows/browser/wmi_admintools)
  2. Published

Exploit prediction

71.74% chance of exploitation in the next 30 days, higher than 99.4% of all scored CVEs (FIRST EPSS, 2026-11-09).

Exploits and checks

  • Metasploit exploit/windows/browser/wmi_admintools Microsoft WMI Administration Tools ActiveX Buffer Overflow metasploit exploit, great rank, 2010-12-21
  • EDB-16516 Microsoft WMI Administration Tools - ActiveX Buffer Overflow (Metasploit) remote, 2011-01-14
  • EDB-15809 Microsoft WMITools - ActiveX Remote Command Execution remote, 2010-12-22
  • wooyun.org http://www.wooyun.org/bug.php?action=view&id=1006 referenced PoC, tagged "exploit" by a source, unverified
  • securityfocus.com http://www.securityfocus.com/bid/45546 referenced PoC, tagged "exploit" by a source, unverified

CVSS scores

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

Classification

Weakness
  • CWE-94 Improper Control of Generation of Code

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.