dbcve.org
Windows 10 1809Operating system · Microsoft

CVE-2025-49723

HIGH · 8.8 CVSS v3.1 Published 2025-07-08
Fix available
A fix is available. Upgrade to 10.0.17763.7558 / 10.0.19044.6093 or later.
See remediation →
90/100
Remediation priority · Urgent
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 authorization in Windows StateRepository API allows an authorized attacker to perform tampering 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 missing authorization vulnerability in the Windows StateRepository API. An authorized attacker (meaning someone with valid credentials but not necessarily admin privileges) can perform local tampering due to insufficient authorization checks in the StateRepository component. The vulnerability allows manipulation of system state that should be restricted.

MitigationApply Microsoft security updates for CVE-2025-49723 once available. Until then, restrict local access to trusted administrators only and monitor for suspicious tampering of Windows StateRepository data.

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.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
Windows Server 2019Operating system
Affected:< 10.0.17763.7558
Windows Server 2022Operating system
Affected:< 10.0.20348.3932

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
Changed
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:L/AC:L/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 installed Windows build version
    Open Command Prompt or PowerShell and run `winver` or execute `[System.Environment]::OSVersion.Version` and note the full build number (e.g., 10.0.19045.6093)
    Affected if The build number is lower than the version listed for your Windows edition in the affected products list
  2. Identify exact Windows edition and build
    Run `systeminfo | findstr /B /C:"OS Name" /C:"OS Version"` to confirm the Windows edition (e.g., Windows 10 22h2, Windows 11 23h2, Windows Server 2022)
    Affected if The identified edition combined with its build number falls below the version threshold specified for that product in the affected range
  3. Verify StateRepository service status
    Open Services console (services.msc) or run `Get-Service StateRepository` in PowerShell to confirm if the StateRepository service exists and is running
    Affected if The service is present and running on a Windows version that is within the affected version ranges (this confirms the vulnerable component is active)
  4. Check current user access context
    Run `whoami /groups` to list current user group memberships and determine privilege level
    Affected if The user has local access credentials on a system running an affected Windows version (the vulnerability allows any local user with valid credentials to potentially exploit the authorization bypass)

A system is affected if it runs any Windows version within the specified build ranges for Windows 10 (1809, 21h2, 22h2), Windows 11 (22h2, 23h2, 24h2), Windows Server 2019, or Windows Server 2022, and the StateRepository service is present.

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.7558 / 10.0.19044.6093 / 10.0.19045.6093 or later
Fixed in 10.0.17763.755810.0.19044.609310.0.19045.6093
Interim mitigation

Apply Microsoft security updates for CVE-2025-49723 once available. Until then, restrict local access to trusted administrators only and monitor for suspicious tampering of Windows StateRepository data.

Recommended fix High confidence

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.5624 | Windows 11 24h2: 10.0.26100.4652 | Windows Server 2019: 10.0.17763.7558 | Windows Server 2022: 10.0.20348.3932

  1. Open Windows Settings and navigate to Update & Security > Windows Update
  2. Click 'Check for updates' to download and install the latest security updates
  3. Alternatively, manually download the security update from the Microsoft Update Catalog for your specific Windows version (KB references can be found on MSRC)
  4. Restart the system after updates are installed
  5. Verify the installed version matches or exceeds the fixed build number for your Windows release
Caveat Standard Windows update apply with no special configuration changes required; ensure regular backup of critical data before any system updates

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

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

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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