dbcve.org
Windows 10 1809Operating system · Microsoft

CVE-2025-24058

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 · high confidence

A local privilege escalation vulnerability exists in the Windows Desktop Window Manager (DWM) Core Library due to improper input validation. An authorized attacker with local access could exploit this vulnerability to gain elevated (higher) privileges on the affected Windows system.

MitigationApply the relevant Microsoft security update for Windows DWM Core Library through Windows Update or manual patch deployment, then verify DWM functionality post-patch.

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. Identify Windows version and build number
    Run `winver` or `systeminfo | findstr /B /C:"OS Name" /C:"OS Version"` to obtain the exact Windows version and build number
    Affected if The build number is lower than the thresholds: 17763.7136 (Windows 10 1809/Server 2019), 19044.5737 (Windows 10 21h2), 19045.5737 (Windows 10 22h2), 22621.5189 (Windows 11 22h2), 22631.5189 (Windows 11 23h2), 26100.3775 (Windows 11 24h2), or 20348.3453 (Windows Server 2022)
  2. Verify DWM Core Library component exists
    Check for the presence of dwmcore.dll in the system directory using `dir C:\Windows\System32\dwmcore.dll`
    Affected if The file dwmcore.dll exists on the system (the vulnerability requires this component to be present)
  3. Confirm DWM service is running
    Run `sc query DwmSvc` or check Task Manager for the Desktop Window Manager (Dwm.exe) process
    Affected if The DWM service is running or the Dwm.exe process is active - this is the component being exploited

A system is affected if it runs a Windows version with a build number lower than the patched thresholds listed for its specific version, and the DWM Core Library component is present and active.

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 relevant Microsoft security update for Windows DWM Core Library through Windows Update or manual patch deployment, then verify DWM functionality post-patch.

Recommended fix High confidence

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 | Windows 11 24h2: build 10.0.26100.3775 | Windows Server 2019: build 10.0.17763.7136 | Windows S

  1. Identify the current Windows version and build number by running 'winver' or 'systeminfo'
  2. Determine which affected version category applies to your system (Windows 10 version, Windows 11 version, or Windows Server)
  3. Apply the appropriate Windows Security Update that includes the fix for CVE-2025-24058
  4. Alternatively, enable automatic Windows Updates to receive the security patch automatically
  5. After updating, verify the build number matches or exceeds the fixed version for your Windows edition
  6. Restart the system as required to complete the update installation
Caveat Standard Windows update risks apply - ensure backups of critical data before applying updates

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

Fix this in Windows 10 1809 Scoped from the published advisory
  • Consultation4.0 h
  • Implementation2.0 h
  • Testing6.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,420
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,872.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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