dbcve.org
Windows Security AppApplication · Microsoft

CVE-2025-47956

MEDIUM · 5.5 CVSS v3.1 Published 2025-06-10
Fix available
A fix is available. Upgrade to 1000.27840.0.1000 or later.
See remediation →
57/100
Remediation priority · Elevated
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
External control of file name or path in Windows Security App allows an authorized attacker to perform spoofing 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 Security App has a path traversal vulnerability where an authorized local attacker can manipulate file paths to perform spoofing attacks. This external control of file name or path allows the attacker to impersonate other users or processes on the local system.

MitigationApply the Microsoft security update for CVE-2025-47956 once released. Until the patch is available, limit local user privileges and monitor for suspicious file access patterns in the Windows Security App.

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 Security AppApplication
Affected:< 1000.27840.0.1000

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
None
Availability
None

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N

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 Security App installation path
    Check if the Windows Security App is installed by looking in the WindowsApps folder. The typical path is C:\Program Files\WindowsApps\Microsoft.WindowsSecurityHub_*, or use PowerShell: Get-AppxPackage -Name Microsoft.WindowsSecurityHub
    Affected if The app is not found or not installed means this specific vulnerability does not apply
  2. Retrieve the installed version number
    Run PowerShell command: (Get-AppxPackage -Name Microsoft.WindowsSecurityHub).Version. This displays the exact version string of the Windows Security App
    Affected if No version is returned indicates the app is not installed on this system
  3. Compare installed version against vulnerable range
    Compare the retrieved version number to the affected threshold: 1000.27840.0.1000. Versions below this value (e.g., 1000.27830.0.0, 1000.27000.0.0) are considered vulnerable
    Affected if The installed version is less than 1000.27840.0.1000 indicates the system is affected by this CVE
  4. Verify local user access context
    Check if non-privileged local user accounts exist on the system using: Get-LocalUser. The vulnerability requires an authorized local attacker to exploit the path traversal
    Affected if Multiple local user accounts exist and the Windows Security App version is below the threshold, the attack surface is present

A system is affected if the Windows Security App is installed with a version lower than 1000.27840.0.1000 and local user accounts exist on the machine.

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 1000.27840.0.1000 or later
Fixed in 1000.27840.0.1000
Interim mitigation

Apply the Microsoft security update for CVE-2025-47956 once released. Until the patch is available, limit local user privileges and monitor for suspicious file access patterns in the Windows Security App.

Recommended fix Moderate confidence

Windows Security App version 1000.27840.0.1000 or later (via Windows Update or Microsoft Store)

  1. Open Windows Settings and navigate to Windows Update
  2. Check for and install any pending updates that include the Windows Security App version 1000.27840.0.1000 or later
  3. Alternatively, open Microsoft Store and check for updates to the Windows Security App
  4. Verify the installed version by opening Windows Security App > Settings > About, confirming the version is 1000.27840.0.1000 or higher
  5. Restart the device if prompted to complete the update installation

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

Fix this in Windows Security App Scoped from the published advisory
  • Consultation4.0 h
  • Testing2.0 h
  • Review / QA2.0 h
8.0 hours of engineering $1,460
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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