dbcve.org
Windows 10 1507Operating system · Microsoft

CVE-2025-54111

HIGH · 7.8 CVSS v3.1 Published 2025-09-09
Fix available
A fix is available. Upgrade to 10.0.10240.21128 / 10.0.14393.8422 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
Use after free in Windows UI XAML Phone DatePickerFlyout 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 use-after-free vulnerability exists in the Windows UI XAML Phone DatePickerFlyout component. This memory corruption flaw allows a locally authenticated attacker to manipulate memory after it has been freed, potentially achieving elevated privileges on the affected system.

MitigationApply the Microsoft security update for CVE-2025-54111 via Windows Update or enterprise patch management systems. Prioritize workstations and systems where untrusted users have local access, as this enables local privilege escalation.

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.21128
Windows 10 1607Operating system
Affected:< 10.0.14393.8422
Windows 10 1809Operating system
Affected:< 10.0.17763.7792
Windows 10 21h2Operating system
Affected:< 10.0.19044.6332
Windows 10 22h2Operating system
Affected:< 10.0.19045.6332
Windows 11 22h2Operating system
Affected:< 10.0.22621.5909
Windows 11 23h2Operating system
Affected:< 10.0.22631.5909
Windows 11 24h2Operating system
Affected:< 10.0.26100.6508

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
High
Privileges
Low
User interaction
None
Scope
Changed
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:C/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 version and build number
    Open Command Prompt or PowerShell and run: winver or systeminfo | findstr /B /C:"OS Name" /C:"OS Version" /C:"Build Number"
    Affected if The build number is lower than the threshold for your Windows version (10.0.10240.21128 for 1507, 10.0.14393.8422 for 1607, 10.0.17763.7792 for 1809, 10.0.19044.6332 for 21h2, 10.0.19045.6332 for 22h2, 10.0.22621.5909 for Win11 22h2, 10.0.22631.5909 for Win11 23h2, 10.0.26100.6508 for Win11 24h2)
  2. Confirm Windows edition
    Run "winver" or check System Properties to confirm whether you are running Windows 10 or Windows 11, and identify the specific release (such as 1507, 1607, 1809, 21h2, 22h2, or the Windows 11 release like 22h2, 23h2, 24h2)
    Affected if The detected edition and release corresponds to an affected version range with a build number below the fixed version
  3. Verify installed Windows updates
    Open Settings > Windows Update > Update history, or run "Get-HotFix" in PowerShell to list installed security updates
    Affected if No security update for CVE-2025-54111 appears in the installed updates list

You are affected if your Windows build number is below the threshold for your specific Windows version and release, and the CVE-2025-54111 security update is not installed.

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.21128 / 10.0.14393.8422 / 10.0.17763.7792 or later
Fixed in 10.0.10240.2112810.0.14393.842210.0.17763.7792
Interim mitigation

Apply the Microsoft security update for CVE-2025-54111 via Windows Update or enterprise patch management systems. Prioritize workstations and systems where untrusted users have local access, as this enables local privilege escalation.

Recommended fix High confidence

Windows 10 1507: 10.0.10240.21128 | Windows 10 1607: 10.0.14393.8422 | Windows 10 1809: 10.0.17763.7792 | Windows 10 21h2: 10.0.19044.6332 | Windows 10 22h2: 10.0.19045.6332 | Windows 11 22h2: 10.0.22621.5909 | Windows 11 23h2: 10.0.22631.5909 | Windows 11 24h2: 10.0.26100.6508

  1. Open Windows Settings by pressing Win+I
  2. Navigate to 'Update & Security' and click 'Windows Update'
  3. Click 'Check for updates' to download and install the latest security updates
  4. Restart the computer when prompted to complete the installation
  5. Verify the installed version by running 'winver' command to confirm the build number matches or exceeds the fixed version for your Windows release
Caveat Standard Windows update risks apply - ensure critical data is backed up 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-54111 — 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-54111 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