Skip to content
vulnerability

CVE-2024-43573

6.5
Medium
KEV · Exploited in wildEPSS 46%Patch available

Windows MSHTML Platform Spoofing Vulnerability

exploited
Yes, in CISA KEV since 8 Oct 2024fix by 29 Oct 2024 (CISA deadline for US federal agencies)
fix
Patch available see the advisory in the references
likelihood
EPSS 46.1%
Published 8 Oct 2024Analysed here 2 Nov 2026CVSS scored by the publisher (CNA)

do firstApply mitigations per vendor instructions or discontinue use of the product if mitigations are unavailable.

triage
client-sideruntimeWAF can block: yesAV · networkCWE-79· Cross-Site Scripting (XSS)

Can a WAF block it? Yes. Cross-site scripting sends script tags or event handlers in the request, which WAF signatures match well.

Also consider: CSP · output encoding

Based on the weakness type only; no CVE-specific evidence yet. We check Cloudflare, AWS, Google Cloud Armor and Azure; for Akamai, Imperva, Fastly, F5, ask your vendor.

cvss vector
attack vectornetworkattack complexitylowprivileges requirednoneuser interactionrequiredscopeunchangedconfidentialityhighintegritynoneavailabilitynone
CVSS 3.1 · CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:N/A:N
common questions

Is CVE-2024-43573 being exploited?

Yes. CVE-2024-43573 appears in CISA's Known Exploited Vulnerabilities catalog, which means exploitation in the wild has been confirmed and reported. Treat it as active rather than theoretical, and patch it ahead of higher-scoring vulnerabilities that carry no exploitation evidence.

How severe is CVE-2024-43573?

CVE-2024-43573 is rated Medium with a CVSS score of 6.5. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.

Is there a patch for CVE-2024-43573?

Yes. A fix has been recorded for CVE-2024-43573. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.

What does CVE-2024-43573 affect?

CVE-2024-43573 affects microsoft:windows_10_1507, microsoft:windows_10_1607, microsoft:windows_10_1809, microsoft:windows_10_21h2, and 10 further products or versions. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.

Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.

executive summary
technical analysis
affected
microsoft:windows_10_1507microsoft:windows_10_1607microsoft:windows_10_1809microsoft:windows_10_21h2microsoft:windows_10_22h2microsoft:windows_11_21h2microsoft:windows_11_22h2microsoft:windows_11_23h2microsoft:windows_11_24h2microsoft:windows_server_2012microsoft:windows_server_2016microsoft:windows_server_2019microsoft:windows_server_2022microsoft:windows_server_2022_23h2
affected versions
Microsoft Windows 10 Version 1507
  • affected>= 10.0.10240.0 and < 10.0.10240.20796
Microsoft Windows 10 Version 1607
  • affected>= 10.0.14393.0 and < 10.0.14393.7428
Microsoft Windows 10 Version 1809
  • affected>= 10.0.17763.0 and < 10.0.17763.6414
Microsoft Windows 10 Version 21H2
  • affected>= 10.0.19043.0 and < 10.0.19044.5011
Microsoft Windows 10 Version 22H2
  • affected>= 10.0.19045.0 and < 10.0.19045.5011
Microsoft Windows 11 version 21H2
  • affected>= 10.0.22000.0 and < 10.0.22000.3260
Microsoft Windows 11 version 22H2
  • affected>= 10.0.22621.0 and < 10.0.22621.4317
Microsoft Windows 11 version 22H3
  • affected>= 10.0.22631.0 and < 10.0.22631.4317
Microsoft Windows 11 Version 23H2
  • affected>= 10.0.22631.0 and < 10.0.22631.4317
Microsoft Windows 11 Version 24H2
  • affected>= 10.0.26100.0 and < 10.0.26100.2033
Microsoft Windows Server 2012 R2
  • affected>= 6.3.9600.0 and < 6.3.9600.22221
Microsoft Windows Server 2012 R2 (Server Core installation)
  • affected>= 6.3.9600.0 and < 6.3.9600.22221
Microsoft Windows Server 2016
  • affected>= 10.0.14393.0 and < 10.0.14393.7428
Microsoft Windows Server 2016 (Server Core installation)
  • affected>= 10.0.14393.0 and < 10.0.14393.7428
Microsoft Windows Server 2019
  • affected>= 10.0.17763.0 and < 10.0.17763.6414
Microsoft Windows Server 2019 (Server Core installation)
  • affected>= 10.0.17763.0 and < 10.0.17763.6414
Microsoft Windows Server 2022
  • affected>= 10.0.20348.0 and < 10.0.20348.2762
Microsoft Windows Server 2022, 23H2 Edition (Server Core installation)
  • affected>= 10.0.25398.0 and < 10.0.25398.1189

As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.

cisa ssvc

exploitation
active
automatable
no
technical impact
partial

Assessed by CISA 9 Oct 2024 (SSVC 2.0.3).

timeline

  1. 8 Oct 2024Added to CISA KEV (exploited in the wild)
  2. 8 Oct 2024Published · 1 day later
  3. 9 Oct 2024CISA SSVC assessment: exploitation active · 1 day later
  4. 29 Oct 2024CISA remediation due date (US federal agencies) · 19 days later
  5. 19 Aug 2026CVE record last updated · 660 days (about 2 years) later
  6. 2 Nov 2026Analysed by vulneraibility.com · 75 days (about 3 months) later
how to fix
Remediation steps are tailored for users whose stack is affected. Add this technology to your stack to see the fix checklist.
references
NVDCVE.orgCVE DetailsSource
2 references in the CVE record: 1 patch, 1 link
  • Patchmsrc.microsoft.com /update-guide/vulnerability/CVE-2024-43573
  • Linkcisa.gov /known-exploited-vulnerabilities-catalog?field_cve=CVE-2024-43573

sources

  • CVE List (CVE.org): description, affected versions, references; CVE Terms of Use
  • NVD: CVSS and CPE data
  • CISA KEV catalog: exploitation, date added, due date
  • CISA Vulnrichment (ADP): SSVC decision points
  • FIRST EPSS: exploit probability and percentile
  • Summary, impact and triage tags: written by our AI analysis pipeline from the sources above. Check them against the sources.
get alerted

Track only the vulnerabilities that affect your infrastructure.

start for free

© 2026 vulneraibility.com, all rights reserved