NewsCompaniesFlawsGuides
Get the app

CVE-2024-30051

From Exploited flaws, HARD’s guide to the flaws being used in attacks · Checked
This article is about a flaw in Microsoft DWM Core Library. For every flaw being used in attacks, see Exploited flaws; for Microsoft’s, see Microsoft flaws being used in attacks.

CVE-2024-30051 is a security flaw in Microsoft DWM Core Library, a part of Windows, Microsoft’s operating system. Someone who already has a foothold can use Microsoft DWM Core Library to take full control of the machine. The US Cybersecurity and Infrastructure Security Agency (CISA) added it to its catalog of flaws known to be used in attacks on 14 May 2024, and says ransomware gangs have used it.[1]

Microsoft DWM Core Library is in things households have, such as phones, computers, browsers and everyday apps, so the fix matters at home as much as at work. Fixed in version 10.0.17763.5820, 10.0.20348.2461, 10.0.22000.2960 and 10.0.19044.4412 and others.

Description

CISA calls it a privilege escalation in Microsoft DWM Core Library. In its words: “Microsoft DWM Core Library contains a privilege escalation vulnerability that allows an attacker to gain SYSTEM privileges.”[1]

The underlying weakness is heap buffer overflow (CWE-122), in MITRE’s list of common software weaknesses.[2]

It scores 7.8 out of 10 on the Common Vulnerability Scoring System, which rates it high, scored by the organisation that published the CVE using CVSS 3.1.[2]

Affected versions

NVD’s record lists these fixed versions: in each line, everything before the version shown is affected.[2]

ProductFixed in
Windows 10 Version 180910.0.17763.5820
Windows Server 201910.0.17763.5820
Windows Server 2019 (Server Core installation)10.0.17763.5820
Windows Server 202210.0.20348.2461
Windows 11 version 21H210.0.22000.2960
Windows 10 Version 21H210.0.19044.4412
Windows 11 version 22H210.0.22621.3593
Windows 10 Version 22H210.0.19045.4412

Every device with Microsoft DWM Core Library needs the update.

Exploitation

CISA added it to its catalog of known exploited vulnerabilities on 14 May 2024, within a day of it being made public. CISA lists a flaw only when it has reliable evidence of it being exploited, and gave US federal agencies until 4 Jun 2024 to fix it.[1] CISA says ransomware gangs have used it.

FIRST’s Exploit Prediction Scoring System, which estimates how likely a flaw is to be used in attacks in the next 30 days from what it sees across the internet, puts it at 6%. That’s in the top 8% of the flaws it scores.[4]

CISA assesses it as not automatable: each attack takes some work.

CISA doesn’t say who was attacked, or how.

Fix

Microsoft has published a fix or advice.[3] CISA’s required action: “Apply mitigations per vendor instructions or discontinue use of the product if mitigations are unavailable.”[1]

  1. Update Microsoft DWM Core Library now.Install the latest update from Microsoft on every device that has it, and restart when asked. Then turn on automatic updates, so the next fix arrives on its own.
  2. Check you’re on 10.0.17763.5820 or later.Fixed in version 10.0.17763.5820, 10.0.20348.2461, 10.0.22000.2960 and 10.0.19044.4412 and others. Anything older is what attackers are going after.
  3. If there’s no update, stop using it.CISA’s advice when a flaw being used in attacks has no fix is to stop using the product until it does.

Timeline

DateEvent
The flaw is made public in the National Vulnerability Database, with a severity score of 7.8.[2]
CISA adds it to its catalog of flaws known to be used in attacks, noting that ransomware gangs have used it.[1]
CISA’s deadline for US government agencies to fix it.[1]
FIRST puts the odds of it being used in attacks in the next 30 days at 6%.[4]

See also

Other Microsoft flaws

  • CVE-2026-96951, Microsoft Windows: command injection ·
  • CVE-2026-65660, Microsoft SharePoint: code injection ·
  • CVE-2026-85880, Microsoft Windows: heap-based buffer overflow ·
  • CVE-2026-81963, Microsoft Windows: link following ·
  • CVE-2019-1068, Microsoft SQL Server: remote code execution ·

Other heap buffer overflow flaws

  • CVE-2026-94127, F5 BIG-IP APM: heap-based buffer overflow ·
  • CVE-2025-25249, Fortinet products: heap-based buffer overflow ·
  • CVE-2024-38812, VMware vCenter Server: heap-based buffer overflow ·
  • CVE-2023-4911, GNU C Library: c library buffer overflow ·
  • CVE-2023-27997, Fortinet FortiOS and FortiProxy SSL-VPN: heap-based buffer overflow ·

Added the same day

  • CVE-2024-30040, Microsoft Windows: MSHTML platform security feature bypass ·

Every Microsoft flaw on CISA’s list · Everything added in May 2024

References

  1. ^ Cybersecurity and Infrastructure Security Agency. “Microsoft DWM Core Library Privilege Escalation Vulnerability”. Known Exploited Vulnerabilities Catalog, added 14 May 2024.
  2. ^ National Institute of Standards and Technology. “CVE-2024-30051 Detail”. National Vulnerability Database, published 14 May 2024.
  3. ^ Microsoft. Advisories and fixes: msrc.microsoft.com.
  4. ^ FIRST. “Exploit Prediction Scoring System”. EPSS 0.057, percentile 93.0, 31 Oct 2026.
  5. CVE Program. “CVE-2024-30051”. The official CVE record.

This article is built from CISA’s catalog (version 2026.10.30), NVD’s record and FIRST’s scores, kept in HARD’s database and checked every morning. The plain English is HARD’s.