dbcve.org
Windows 10 1507Operating system · Microsoft

CVE-2025-24071

MEDIUM · 6.5 CVSS v3.1 Published 2025-03-11
Fix available
A fix is available. Upgrade to 10.0.10240.20947 / 10.0.14393.7876 or later.
See remediation →
72/100
Remediation priority · Elevated
Public exploit Remotely reachable No privileges

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
Exposure of sensitive information to an unauthorized actor in Windows File Explorer allows an unauthorized attacker to perform spoofing over a network.

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
How this class of weakness works · CWE-200

The application discloses data — error detail, internal paths, tokens, or other users' records — to someone who shouldn't see it. On its own it can look minor, but it hands attackers the map they need for a larger attack. Remediation is about minimising what's returned and enforcing authorization on every piece of data.

General guidance for the information exposure class — the official description and references above are authoritative for this specific CVE. Want a bespoke review and a reviewed fix? Ask our team →

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.20947
Windows 10 1607Operating system
Affected:< 10.0.14393.7876
Windows 10 1809Operating system
Affected:< 10.0.17763.7009
Windows 11 23h2Operating system
Affected:< 10.0.22631.5039
Windows 11 24h2Operating system
Affected:< 10.0.26100.3476
Windows Server 2012Operating system
Affected:= r2
Windows Server 2016Operating system
Affected:< 10.0.14393.7876
Windows Server 2019Operating system
Affected:< 10.0.17763.7009

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

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

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.20947 / 10.0.14393.7876 / 10.0.17763.7009 or later
Fixed in 10.0.10240.2094710.0.14393.787610.0.17763.7009
Recommended fix Moderate confidence

Windows 10 1507: 10.0.10240.20947 or later | Windows 10 1607: 10.0.14393.7876 or later | Windows 10 1809: 10.0.17763.7009 or later | Windows 11 23h2: 10.0.22631.5039 or later | Windows 11 24h2: 10.0.26100.3476 or later | Windows Server 2016: 10.0.14393.7876 or later | Windows Server 2019: 10.0.17763

  1. Open Windows Update by pressing Windows key + I, then navigating to Update & Security > Windows Update
  2. Click 'Check for updates' and ensure all pending updates are installed
  3. For Windows 10: Navigate to Settings > Update & Security > Windows Update and install the KB patch for this vulnerability (check Windows Update history for the specific KB number)
  4. For Windows 11: Navigate to Settings > Windows Update and install the KB patch for this vulnerability
  5. For Windows Server: Use Windows Update for Business, WSUS, or manually download the applicable KB patch from the Microsoft Update Catalog
  6. After installation, verify the installed version matches or exceeds the fixed build number for your Windows version
  7. Restart the system if prompted to complete the installation
Caveat Standard Windows cumulative update; review release notes for any known compatibility issues before deployment in production environments

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

We can perform the upgrade in your staging environment and verify nothing breaks — typical engagement from $900. Get the upgrade done

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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