CVE-2024-30051
Windows DWM Core Library Elevation of Privilege Vulnerability
- CVSS
- 7.8Highscored by the publisher (CNA)
- Exploited in the wild
- Yes, in CISA KEV since 14 May 2024CISA deadline for US federal agencies: 4 Jun 2024known use in ransomware campaignsunvetted proof-of-concept code on github
- EPSS
- 6.2%chance of exploitation in the next 30 daystop 7% of scored CVEsFIRST score of 11 Nov 2026
- Fix
- Patch availablesee the advisories in the references
- Published
- 14 May 2024analysed here 12 Nov 2026
Do first. Apply mitigations per vendor instructions or discontinue use of the product if mitigations are unavailable. (CISA's required action for this KEV entry)
Summary
Triage
- Attack surface
- Server-side
- Exploitable
- At runtime
- Attack vector
- local
The summary, impact and action text on this page are written by our AI analysis pipeline, or taken from the NVD description when a CVE was imported from NVD. They are not the vendor's wording: check them against the sources. A longer AI executive summary and technical analysis are generated for signed-in accounts on the Max plan.
Affected products
| Product | Affected versions | Vendor says fixed in |
|---|---|---|
| Microsoft Windows 10 Version 1507 | >= 10.0.10240.0 and < 10.0.10240.20651Vendor says fixed in: not stated | |
| Microsoft Windows 10 Version 1607 | >= 10.0.14393.0 and < 10.0.14393.6981Vendor says fixed in: not stated | |
| Microsoft Windows 10 Version 1809 | >= 10.0.17763.0 and < 10.0.17763.5820>= 10.0.0 and < 10.0.17763.5820Vendor says fixed in: not stated | |
| Microsoft Windows 10 Version 21H2 | >= 10.0.19043.0 and < 10.0.19044.4412Vendor says fixed in: not stated | |
| Microsoft Windows 10 Version 22H2 | >= 10.0.19045.0 and < 10.0.19045.4412Vendor says fixed in: not stated | |
| Microsoft Windows 11 version 21H2 | >= 10.0.0 and < 10.0.22000.2960Vendor says fixed in: not stated | |
| Microsoft Windows 11 version 22H2 | >= 10.0.22621.0 and < 10.0.22621.3593Vendor says fixed in: not stated | |
| Microsoft Windows 11 version 22H3 | >= 10.0.22631.0 and < 10.0.22631.3593Vendor says fixed in: not stated | |
| Microsoft Windows 11 Version 23H2 | >= 10.0.22631.0 and < 10.0.22631.3593Vendor says fixed in: not stated | |
| Microsoft Windows Server 2016 | >= 10.0.14393.0 and < 10.0.14393.6981Vendor says fixed in: not stated | |
| Microsoft Windows Server 2016 (Server Core installation) | >= 10.0.14393.0 and < 10.0.14393.6981Vendor says fixed in: not stated | |
| Microsoft Windows Server 2019 | >= 10.0.17763.0 and < 10.0.17763.5820Vendor says fixed in: not stated | |
| Microsoft Windows Server 2019 (Server Core installation) | >= 10.0.17763.0 and < 10.0.17763.5820Vendor says fixed in: not stated | |
| Microsoft Windows Server 2022 | >= 10.0.20348.0 and < 10.0.20348.2461Vendor says fixed in: not stated |
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.
Products named in our analysis
- microsoft:windows_10_1507
- microsoft:windows_10_1607
- microsoft:windows_10_1809
- microsoft:windows_10_21h2
- microsoft:windows_10_22h2
- microsoft:windows_11_21h2
- microsoft:windows_11_22h2
- microsoft:windows_11_23h2
- microsoft:windows_server_2016
- microsoft:windows_server_2019
- microsoft:windows_server_2022
Fix and mitigation
WAF and other mitigations
Can a WAF block it? No. The attack needs local access to the machine, so a WAF is not on its path.
Also consider: patch
Based on the attack vector (local or physical access). We check Cloudflare, AWS, Google Cloud Armor and Azure; for Akamai, Imperva, Fastly, F5, ask your vendor.
Remediation steps (AI-written)
Step-by-step remediation is generated for accounts on the Max plan, for CVEs that match a technology in their stack. Add this technology to your stack to see the fix checklist.
Exploitation evidence
- CISA KEV catalog
- Listed since 14 May 2024. Known use in ransomware campaigns.
- CISA due date
- 4 Jun 2024, the remediation deadline for US federal agencies
- CISA required action
- Apply mitigations per vendor instructions or discontinue use of the product if mitigations are unavailable.
- Public exploit code
- Unvetted proof-of-concept code on GitHub: 2 GitHub proofs of concept
- CISA SSVC
- exploitation active, automatable no, technical impact totalAssessed by CISA 15 May 2024 (SSVC 2.0.3). Exploitation is none, poc (public proof of concept) or active.
GitHub proofs of concept
- fortra/CVE-2024-30051125 stars
- devianntsec/CVE-2024-300511 stars
Listed so you can judge urgency, not as a recommendation to run anything. GitHub “proofs of concept” are unvetted: some are fake or carry malware. Exploit-DB marks the entries its staff verified.
Timeline
- 14 May 2024Added to CISA KEV (exploited in the wild)
- 14 May 2024Published1 day later
- 15 May 2024CISA SSVC assessment: exploitation active1 day later
- 4 Jun 2024CISA remediation due date (US federal agencies)19 days later
- 14 Aug 2024First proof-of-concept repository on GitHub (unvetted)71 days (about 2 months) later
- 21 Oct 2025CVE record last updated434 days (about 1 year) later
- 12 Nov 2026Analysed by vulneraibility.com387 days (about 1 year) later
CVSS vector
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
| Metric | Value | What it means |
|---|---|---|
| Attack vector | LocalLocal access required (shell, logged-in user). | Local access required (shell, logged-in user). |
| Attack complexity | LowRepeatable attack, no special conditions. | Repeatable attack, no special conditions. |
| Privileges required | LowThe attacker needs basic user privileges. | The attacker needs basic user privileges. |
| User interaction | NoneNo victim action needed. | No victim action needed. |
| Scope | UnchangedImpact stays within the vulnerable component. | Impact stays within the vulnerable component. |
| Confidentiality | HighTotal data disclosure possible. | Total data disclosure possible. |
| Integrity | HighComplete modification possible. | Complete modification possible. |
| Availability | HighFull outage possible. | Full outage possible. |
Common questions
Is CVE-2024-30051 being exploited?
Yes. CVE-2024-30051 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-30051?
CVE-2024-30051 is rated High with a CVSS score of 7.8. 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-30051?
Yes. A fix has been recorded for CVE-2024-30051. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2024-30051 affect?
CVE-2024-30051 affects microsoft:windows_10_1507, microsoft:windows_10_1607, microsoft:windows_10_1809, microsoft:windows_10_21h2, and 7 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.
References
2 references in the CVE record, grouped by the tags the record gives them.
Advisories (1)
- msrc.microsoft.com /update-guide/vulnerability/CVE-2024-30051
Other links (1)
- cisa.gov /known-exploited-vulnerabilities-catalog?field_cve=CVE-2024-30051
Where the data on this page comes from
- 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
- PoC-in-GitHub: GitHub repositories that claim a proof of concept
Summary, impact and triage tags: written by our AI analysis pipeline from the sources above. Check them against the sources.
Similar CVEs
Get CVEs like this by email. Join the free digest: the CVEs we flag as major, all CVSS 8.0 or higher, in up to three emails a day (sent at 05:00, 11:00 and 15:00 UTC). Matching alerts to the products you run needs an account, and accounts are invite-only during the beta.