Skip to content
Server Security Center
KEVmedium6.5

CVE-2024-43573: Microsoft Windows MSHTML Platform Spoofing

Microsoft Windows · listed in the CISA catalog of actively exploited vulnerabilities since 2024-10-08.

CVSS v3.1 (CVE record)
6.5
medium
EPSS (exploit probability, 30 days)
46%
higher than 98.8% of all CVEs
Added to CISA KEV
2024-10-08
US federal due date 2024-10-29
Automatable (CISA SSVC)
no
technical impact: partial

CVE-2024-43573 explained

CVE-2024-43573 is an unspecified spoofing vulnerability in the Microsoft Windows MSHTML Platform, classified as cross-site scripting (CWE-79). It can lead to a loss of confidentiality. CISA lists it as known to be exploited, so affected Windows 10, Windows 11 and Windows Server 2012 R2 systems should be updated promptly.

Impact

A remote attacker needs no privileges, but a user must interact, for example by opening attacker-supplied content. Successful exploitation can cause a high loss of confidentiality, with no impact on integrity or availability. CISA rates the technical impact as partial and the attack as not automatable, so it cannot easily be exploited at scale without manual steps. CISA lists it as known to be exploited. Use by ransomware is unknown.

Who is affected

The CVE record lists Windows 10 versions 1507, 1607, 1809, 21H2 and 22H2. Fixed builds include 10.0.10240.20796, 10.0.14393.7428, 10.0.17763.6414, 10.0.19044.5011 and 10.0.19045.5011. Windows 11 versions 21H2, 22H2, 22H3, 23H2 and 24H2 are fixed in 10.0.22000.3260, 10.0.22621.4317, 10.0.22631.4317 and 10.0.26100.2033. Windows Server 2012 R2, including Server Core, is fixed in 6.3.9600.22221. The page lists 6 further products.

Written with AI from the data on this page and checked against it automatically.

Official description

Microsoft Windows MSHTML Platform contains an unspecified spoofing vulnerability which can lead to a loss of confidentiality.

CISA required action: Apply mitigations per vendor instructions or discontinue use of the product if mitigations are unavailable.

CISA notes

Affected and fixed versions

From the CVE record published by the vendor or CVE numbering authority.

  • Microsoft Windows 10 Version 150732-bit, x64
    Affected
    • < 10.0.10240.20796
    Fixed in
    • 10.0.10240.20796
  • Microsoft Windows 10 Version 160732-bit, x64
    Affected
    • < 10.0.14393.7428
    Fixed in
    • 10.0.14393.7428
  • Microsoft Windows 10 Version 180932-bit, x64
    Affected
    • < 10.0.17763.6414
    Fixed in
    • 10.0.17763.6414
  • Microsoft Windows 10 Version 21H232-bit, ARM64, x64
    Affected
    • < 10.0.19044.5011
    Fixed in
    • 10.0.19044.5011
  • Microsoft Windows 10 Version 22H232-bit, ARM64, x64
    Affected
    • < 10.0.19045.5011
    Fixed in
    • 10.0.19045.5011
  • Microsoft Windows 11 version 21H2ARM64, x64
    Affected
    • < 10.0.22000.3260
    Fixed in
    • 10.0.22000.3260
  • Microsoft Windows 11 version 22H2ARM64, x64
    Affected
    • < 10.0.22621.4317
    Fixed in
    • 10.0.22621.4317
  • Microsoft Windows 11 version 22H3ARM64
    Affected
    • < 10.0.22631.4317
    Fixed in
    • 10.0.22631.4317
  • Microsoft Windows 11 Version 23H2x64
    Affected
    • < 10.0.22631.4317
    Fixed in
    • 10.0.22631.4317
  • Microsoft Windows 11 Version 24H2ARM64, x64
    Affected
    • < 10.0.26100.2033
    Fixed in
    • 10.0.26100.2033
Show 8 more products
  • Microsoft Windows Server 2012 R2x64
    Affected
    • < 6.3.9600.22221
    Fixed in
    • 6.3.9600.22221
  • Microsoft Windows Server 2012 R2 (Server Core installation)x64
    Affected
    • < 6.3.9600.22221
    Fixed in
    • 6.3.9600.22221
  • Microsoft Windows Server 2016x64
    Affected
    • < 10.0.14393.7428
    Fixed in
    • 10.0.14393.7428
  • Microsoft Windows Server 2016 (Server Core installation)x64
    Affected
    • < 10.0.14393.7428
    Fixed in
    • 10.0.14393.7428
  • Microsoft Windows Server 2019x64
    Affected
    • < 10.0.17763.6414
    Fixed in
    • 10.0.17763.6414
  • Microsoft Windows Server 2019 (Server Core installation)x64
    Affected
    • < 10.0.17763.6414
    Fixed in
    • 10.0.17763.6414
  • Microsoft Windows Server 2022x64
    Affected
    • < 10.0.20348.2762
    Fixed in
    • 10.0.20348.2762
  • Microsoft Windows Server 2022, 23H2 Edition (Server Core installation)x64
    Affected
    • < 10.0.25398.1189
    Fixed in
    • 10.0.25398.1189

How to fix it

  • Update to the fixed version for your product:
    • Microsoft Windows 10 Version 1507: 10.0.10240.20796
    • Microsoft Windows 10 Version 1607: 10.0.14393.7428
    • Microsoft Windows 10 Version 1809: 10.0.17763.6414
    • Microsoft Windows 10 Version 21H2: 10.0.19044.5011
    • Microsoft Windows 10 Version 22H2: 10.0.19045.5011
    • Microsoft Windows 11 version 21H2: 10.0.22000.3260
    Fixed versions for 12 more products are in the table above.
  • Vendor advisory: msrc.microsoft.com/update-guide/vulnerability/CVE-2024-43573
  • CISA's deadline for US federal agencies: 2024-10-29 (passed) – a useful benchmark for everyone else, too.

What to do

  1. Install Microsoft's security update that brings each system to at least the fixed build listed for its Windows version.
  2. Prioritize patching because CISA lists this vulnerability as known to be exploited.
  3. Follow the Microsoft advisory for the further listed products and any additional guidance.
  4. Make users aware of the risk of opening untrusted links and files, since exploitation requires user interaction.
  5. Review systems for signs of compromise if patching was delayed.

Written with AI from the data on this page and checked against it automatically.

CISA's assessment (SSVC)

Exploitation
Exploited in the wild
Automatable
No – each attack needs manual steps
Technical impact
Partial – limited control or information

Weakness: CWE-79 Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting')

Questions about CVE-2024-43573

Is CVE-2024-43573 being exploited?
Yes. CISA added it to its Known Exploited Vulnerabilities catalog on 2024-10-08, with a US federal due date of 2024-10-29. Whether it has been used in ransomware campaigns is unknown.
Can it be exploited without user action?
No. The CVSS vector requires user interaction, although the attacker needs no privileges and can attack over the network.
What does an attacker gain?
The vulnerability can lead to a high loss of confidentiality. The record lists no impact on integrity or availability.

Written with AI from the data on this page and checked against it automatically.

References

Data: CISA Known Exploited Vulnerabilities (public domain) · CVE Program records incl. CISA ADP enrichment · OSV.dev (CC BY 4.0) incl. Ubuntu and Debian security data · FIRST EPSS · endoflife.date. Updated automatically – facts last changed 2026-11-21. Always confirm with the vendor's or distribution's advisory before patching.