Skip to content
Fencer Vulns
high 7.6

CVE-2006-5745 in the critical feed json

Unspecified vulnerability in the setRequestHeader method in the XMLHTTP (XML HTTP) ActiveX Control 4.0 in Microsoft XML Core Services 4.0 o…

published 2006-11-06 20 y ago modified 2026-06-16 4 mo ago also EUVD-2006-5729

cvss
7.6
version 2.0, NVD
cisa kev
Not listed
not in CISA's catalog
epss
77.6%
EPSS 77.6% chance of exploitation in 30 days, percentile 99.5%
public exploits
5
Metasploit, Exploit-DB

Summary

Unspecified vulnerability in the setRequestHeader method in the XMLHTTP (XML HTTP) ActiveX Control 4.0 in Microsoft XML Core Services 4.0 on Windows, when accessed by Internet Explorer, allows remote attackers to execute arbitrary code via crafted arguments that lead to memory corruption, a different vulnerability than CVE-2006-4685. NOTE: some of these details are obtained from third party information.

Timeline

  1. First public exploit (Metasploit exploit/windows/browser/ms06_071_xml_core)
  2. Published

Exploit prediction

77.59% chance of exploitation in the next 30 days, higher than 99.5% of all scored CVEs (FIRST EPSS, 2026-11-08).

Exploits and checks

  • Metasploit exploit/windows/browser/ms06_071_xml_core MS06-071 Microsoft Internet Explorer XML Core Services HTTP Request Handling metasploit exploit, normal rank, 2006-10-10
  • EDB-16532 Microsoft Internet Explorer - XML Core Services HTTP Request Handling (MS06-071) (Metasploit) remote, 2010-07-03
  • EDB-2753 Microsoft Internet Explorer 6/7 - XML Core Services Remote Code Execution (3) remote, 2006-11-10
  • EDB-2749 Microsoft Internet Explorer 6/7 - XML Core Services Remote Code Execution (2) remote, 2006-11-10
  • EDB-2743 Microsoft Internet Explorer 6/7 - XML Core Services Remote Code Execution (1) remote, 2006-11-08
  • securityfocus.com http://www.securityfocus.com/bid/20915 referenced PoC, tagged "exploit" by a source, unverified

CVSS scores

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

References

Sources

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