dbcve.org
Windows 10 1507Operating system · Microsoft

CVE-2025-53789

HIGH · 7.8 CVSS v3.1 Published 2025-08-12
Fix available
A fix is available. Upgrade to 10.0.10240.21073 / 10.0.14393.8246 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
Missing authentication for critical function in Windows StateRepository API 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

The Windows StateRepository API lacks proper authentication checks on a critical function, allowing a locally authorized attacker to execute code at a higher privilege level. This privilege escalation occurs because the vulnerable API endpoint does not validate user credentials before performing privileged operations.

MitigationApply the Microsoft security update for CVE-2025-53789 to all affected Windows systems. Since this is a local privilege escalation, ensure attackers cannot achieve initial access through other means.

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.21073
Windows 10 1607Operating system
Affected:< 10.0.14393.8246
Windows 10 1809Operating system
Affected:< 10.0.17763.7558
Windows 10 21h2Operating system
Affected:< 10.0.19044.6093
Windows 10 22h2Operating system
Affected:< 10.0.19045.6093
Windows 11 22h2Operating system
Affected:< 10.0.22621.5624
Windows 11 23h2Operating system
Affected:<= 10.0.22631.5624
Windows 11 24h2Operating system
Affected:< 10.0.26100.4652

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
    Open Command Prompt or PowerShell and run 'winver' or 'systeminfo | findstr /C:"Build"' to obtain the OS build number
    Affected if The build number falls below any of these thresholds: 10240.21073 (Win10 1507), 14393.8246 (Win10 1607), 17763.7558 (Win10 1809), 19044.6093 (Win10 21h2/22h2), 22621.5624 (Win11 22h2), 22631.5624 (Win11 23h2), or 26100.4652 (Win11 24h2)
  2. Verify exact Windows version
    Run 'winver' to confirm the specific Windows release (such as 1507, 1607, 1809, 21h2, 22h2, 22h2, 23h2, or 24h2)
    Affected if The identified Windows release version matches one listed in the affected products and its build number is lower than the corresponding threshold
  3. Confirm StateRepository service presence
    Check if the StateRepository service exists by running 'Get-Service StateRepository' in PowerShell or viewing services list in services.msc
    Affected if The StateRepository service is present and running on the system (required for the vulnerability to be exploitable)

You are affected if your Windows build number is lower than the threshold for your specific Windows release version AND the StateRepository service is present on your system.

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.21073 / 10.0.14393.8246 / 10.0.17763.7558 or later
Fixed in 10.0.10240.2107310.0.14393.824610.0.17763.7558
Interim mitigation

Apply the Microsoft security update for CVE-2025-53789 to all affected Windows systems. Since this is a local privilege escalation, ensure attackers cannot achieve initial access through other means.

Recommended fix High confidence

Windows 10 1507: 10.0.10240.21073+ | Windows 10 1607: 10.0.14393.8246+ | Windows 10 1809: 10.0.17763.7558+ | Windows 10 21h2: 10.0.19044.6093+ | Windows 10 22h2: 10.0.19045.6093+ | Windows 11 22h2: 10.0.22621.5624+ | Windows 11 23h2: 10.0.22631.5625+ | Windows 11 24h2: 10.0.26100.4652+

  1. Identify the current Windows version by running 'winver' or 'systeminfo' in Command Prompt
  2. Open Settings > Update & Security > Windows Update and check for available updates
  3. Install all cumulative updates and security updates to reach the fixed version
  4. Restart the system as required by the updates
  5. Verify the version has been updated to a patched release using 'winver'
Caveat Standard Windows update risks - may require restart; verify application compatibility after updating

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

Fix this in Windows 10 1507 Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,860
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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