dbcve.org
Windows 10 1809Operating system · Microsoft

CVE-2025-24060

HIGH · 7.8 CVSS v3.1 Published 2025-04-08
Fix available
A fix is available. Upgrade to 10.0.17763.7136 / 10.0.19044.5737 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

Improper input validation in Windows DWM Core Library (dwmcore.dll) allows a local authenticated attacker to execute arbitrary code with elevated (SYSTEM) privileges by exploiting insufficient validation of input parameters passed to DWM core functions.

MitigationApply the Microsoft security update for CVE-2025-24060 via Windows Update or enterprise patch management deployment to all affected Windows systems.

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 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
Windows Server 2019Operating system
Affected:< 10.0.17763.7136
Windows Server 2022Operating system
Affected:< 10.0.20348.3453

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. Check Windows build number
    Run 'winver' or 'systeminfo | findstr /B /C:"OS Version"' to obtain the full build number including the minor version (e.g., 17763.7136)
    Affected if The build number is lower than the fixed builds: 17763.7136 for Windows 10 1809/Server 2019, 19044.5737 for Windows 10 21h2, 19045.5737 for Windows 10 22h2, 22621.5189 for Windows 11 22h2, 22631.5189 for Windows 11 23h2, 26100.3775 for Windows 11 24h2, or 20348.3453 for Windows Server 2022
  2. Identify Windows release version
    Run 'winver' or check 'systeminfo' to determine if the system is Windows 10 1809, 21h2, 22h2, Windows 11 22h2, 23h2, 24h2, Windows Server 2019, or Windows Server 2022
    Affected if The system matches any of the affected product releases listed in the CVE
  3. Verify DWM Core Library is present
    Confirm dwmcore.dll exists in the System32 directory using 'dir C:\Windows\System32\dwmcore.dll' - this DLL is part of the Desktop Window Manager core and is present on all supported Windows systems with DWM enabled
    Affected if The DLL is present (this is the component with the input validation vulnerability)

The system is affected if it runs any of the listed Windows versions with a build number lower than the corresponding fixed build for that release.

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.17763.7136 / 10.0.19044.5737 / 10.0.19045.5737 or later
Fixed in 10.0.17763.713610.0.19044.573710.0.19045.5737
Interim mitigation

Apply the Microsoft security update for CVE-2025-24060 via Windows Update or enterprise patch management deployment to all affected Windows systems.

Recommended fix High confidence

Install the March 2025 Windows Security Update (KB5002537 or subsequent cumulative update) which includes the fix for CVE-2025-24060

  1. Open Windows Update (Settings > Update & Security > Windows Update)
  2. Click 'Check for updates' to download and install the latest security updates
  3. Restart the system after updates are installed
  4. Verify the installed KB by running: Get-HotFix | Where-Object {$_.Description -eq 'Security Update'} | Sort-Object InstalledOn -Descending | Select-Object -First 1
  5. Alternatively, verify the build version matches or exceeds: winver (for desktop) or systeminfo | findstr /B /C:"OS Build" (for servers)
Caveat Standard Windows update - no expected breaking changes; as a privilege escalation fix, apply promptly

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

Fix this in Windows 10 1809 Scoped from the published advisory
  • Consultation2.0 h
  • Implementation6.0 h
  • Testing4.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,440
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-24060 — 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-24060 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