dbcve.org
Windows 10 1507Operating system · Microsoft

CVE-2025-54116

HIGH · 7.3 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 →
73/100
Remediation priority · Elevated

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 access control in Windows MultiPoint Services 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 access control in Windows MultiPoint Services allows an authorized attacker to elevate privileges locally. This is a local privilege escalation vulnerability where the access control mechanism fails to properly restrict actions, enabling a user with existing authorized access to gain higher-level permissions on the system.

MitigationApply the Microsoft security update for CVE-2025-54116 when available through Windows Update or Microsoft Update Catalog. Prior to deployment, document current MultiPoint Services configurations and verify backup availability. After patching, validate that MultiPoint Services functionality remains intact.

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

CVSS:3.1/AV:L/AC:L/PR:L/UI:R/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 if MultiPoint Services is installed
    Open PowerShell and run: Get-WindowsFeature -Name MultiPoint-Services (on Server) or check Services.msc for 'MultiPoint Services' service presence on desktop Windows
    Affected if MultiPoint Services is not installed or not present on the system, the vulnerability does not apply
  2. Verify Windows version
    Run 'winver' from Run dialog or use PowerShell: [System.Environment]::OSVersion.Version or Get-ComputerInfo | Select WindowsVersion, OsVersion
    Affected if The installed Windows version falls within any of these ranges: Win10 1507 < 10.0.10240.21128, Win10 1607 < 10.0.14393.8422, Win10 1809 < 10.0.17763.7792, Win10 21h2 < 10.0.19044.6332, Win10 22h2 < 10.0.19045.6332, Win11 22h2 < 10.0.22621.5909, Win11 23h2 < 10.0.22631.5909, Win11 24h2 < 10.0.26100.6
  3. Confirm MultiPoint Services is running
    Run 'Get-Service -Name *MultiPoint*' in PowerShell or check the MultiPoint Services status in Services console
    Affected if The MultiPoint Services service is installed and running while the Windows version is below the fixed builds listed above

You are affected if Windows MultiPoint Services is installed/running AND your Windows version is below the specific build number for your Windows release (10.0.10240.21128, 10.0.14393.8422, 10.0.17763.7792, 10.0.19044.6332, 10.0.19045.6332, 10.0.22621.5909, 10.0.22631.5909, or 10.0.26100.6508).

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-54116 when available through Windows Update or Microsoft Update Catalog. Prior to deployment, document current MultiPoint Services configurations and verify backup availability. After patching, validate that MultiPoint Services functionality remains intact.

Recommended fix High confidence

Apply Windows Security Update for CVE-2025-54116 to reach the minimum fixed build: Windows 10 1507 to 10.0.10240.21128 | Windows 10 1607 to 10.0.14393.8422 | Windows 10 1809 to 10.0.17763.7792 | Windows 10 21h2 to 10.0.19044.6332 | Windows 10 22h2 to 10.0.19045.6332 | Windows 11 22h2 to 10.0.22621.5

  1. Identify the current Windows build version by running 'winver' or 'systeminfo' in Command Prompt
  2. Determine which Windows 10 or 11 version and build is installed (1507, 1607, 1809, 21h2, 22h2, 11 22h2, 11 23h2, or 11 24h2)
  3. Apply the appropriate Windows Security Update from Microsoft's Security Response Center (msrc.microsoft.com) that addresses CVE-2025-54116
  4. Verify the installation completed successfully by checking the updated build version matches or exceeds the fixed version for your Windows release
  5. Restart the system if prompted to complete the update installation
Caveat Standard Windows update deployment considerations apply - test updates in staging environment before broad deployment to avoid disrupting production systems

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
  • Implementation3.0 h
  • Testing4.0 h
  • Review / QA2.0 h
13.0 hours of engineering $2,300
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,680.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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