dbcve.org
Windows 10 1507Operating system · Microsoft

CVE-2025-24073

HIGH · 7.8 CVSS v3.1 Published 2025-04-08
Fix available
A fix is available. Upgrade to 10.0.10240.20978 / 10.0.14393.7969 or later.
See remediation →
80/100
Remediation priority · High
Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
Improper input validation in Windows DWM Core Library allows an authorized attacker to elevate privileges locally.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · moderate confidence

This is a local privilege escalation vulnerability in the Windows Desktop Window Manager (DWM) Core Library caused by improper input validation. An authorized attacker who already has local access to a vulnerable Windows system can exploit this flaw to elevate their privileges, likely achieving higher integrity levels or administrative rights.

MitigationApply the relevant Microsoft security update for CVE-2025-24073 through Windows Update or enterprise patch management to remediate the input validation flaw in the DWM Core Library.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Windows 10 1507Operating system
Affected:< 10.0.10240.20978
Windows 10 1607Operating system
Affected:< 10.0.14393.7969
Windows 10 1809Operating system
Affected:< 10.0.17763.7136
Windows 10 21h2Operating system
Affected:< 10.0.19044.5737
Windows 10 22h2Operating system
Affected:< 10.0.19045.5737
Windows 11 22h2Operating system
Affected:< 10.0.22621.5189
Windows 11 23h2Operating system
Affected:< 10.0.22631.5189
Windows 11 24h2Operating system
Affected:< 10.0.26100.3775

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Local
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify your Windows version
    Run 'winver' or 'systeminfo | findstr /B /C:"OS Name" /C:"OS Version"' to get the exact Windows build number
    Affected if The build number falls below any of these thresholds: 10240.20978, 14393.7969, 17763.7136, 19044.5737, 19045.5737, 22621.5189, 22631.5189, or 26100.3775 depending on your Windows 10/11 release
  2. Check the DWM Core Library file version
    Open PowerShell and run: (Get-Item C:\Windows\System32\dwmcore.dll).VersionInfo | Select-Object FileVersion, ProductVersion
    Affected if The dwmcore.dll file version is lower than the version corresponding to your Windows build's fixed release (compare against Microsoft's security update KB for this CVE)
  3. Verify the Desktop Window Manager service status
    Run 'services.msc' and check the Desktop Window Manager (DWM) service, or run 'sc query DWM' in Command Prompt
    Affected if The DWM service is running (this is required for the vulnerable code path to be active; however, note that DWM is typically enabled by default on modern Windows)

Your system is likely affected if your Windows build number is below the fixed versions AND the DWM Core Library (dwmcore.dll) version matches the vulnerable version for that build, and DWM is enabled (default state).

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 10.0.10240.20978 / 10.0.14393.7969 / 10.0.17763.7136 or later
Fixed in 10.0.10240.2097810.0.14393.796910.0.17763.7136
Interim mitigation

Apply the relevant Microsoft security update for CVE-2025-24073 through Windows Update or enterprise patch management to remediate the input validation flaw in the DWM Core Library.

Recommended fix High confidence

Upgrade to Windows 10 1507 build 10.0.10240.20978, Windows 10 1607 build 10.0.14393.7969, Windows 10 1809 build 10.0.17763.7136, Windows 10 21h2 build 10.0.19044.5737, Windows 10 22h2 build 10.0.19045.5737, Windows 11 22h2 build 10.0.22621.5189, Windows 11 23h2 build 10.0.22631.5189, or Windows 11 2

  1. Open Settings on the Windows system
  2. Navigate to Update & Security > Windows Update
  3. Click 'Check for updates' and install all available updates
  4. Alternatively, manually download and install the appropriate cumulative update for your Windows version from the Microsoft Update Catalog
  5. Verify the installation by checking the OS build number in Settings > System > About
  6. Confirm the build number matches or exceeds the fixed version for your Windows release
Caveat Standard Windows update—minimal risk; ensure backup of critical data before applying updates

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Windows 10 1507 Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
7.0 hours of engineering $1,240
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,984.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-24073 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-24073 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data