CVE-2006-5745

CVE-2006-5745 is a high-severity vulnerability in Microsoft Xml Core Services with a CVSS 2.0 base score of 7.6. Its EPSS exploit-prediction score of 76% places it in the 99th percentile, indicating an elevated likelihood of exploitation.

Key facts

Description

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.

Frequently asked questions

What is CVE-2006-5745?
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.
How severe is CVE-2006-5745?
CVE-2006-5745 has a CVSS 2.0 base score of 7.6, rated high severity.
Is CVE-2006-5745 being actively exploited?
It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 76% (99th percentile), an estimate of the probability of exploitation in the next 30 days.
What products are affected by CVE-2006-5745?
CVE-2006-5745 affects Microsoft Xml Core Services. See the affected-products list for the exact vulnerable versions.
How do I fix CVE-2006-5745?
Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround. Given its high severity, prioritise patching exposed systems.
When was CVE-2006-5745 published?
CVE-2006-5745 was published on 2006-11-06 and last updated on 2026-06-16.

References

Affected products (1)

More vulnerabilities in Microsoft Xml Core Services

All CVEs affecting Microsoft Xml Core Services →