CVE-2025-47980
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 · uneditedExposure of sensitive information to an unauthorized actor in Windows Imaging Component allows an unauthorized attacker to disclose information 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 confidenceCVE-2025-47980 is a local information disclosure vulnerability in Windows Imaging Component. An unauthenticated attacker with local access can exploit this to read sensitive information from the affected system. The medium severity (CVSS 6.2) reflects that while no privileges or user interaction are required, the attacker needs local access to the machine.
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< 10.0.10240.21073< 10.0.14393.8246< 10.0.17763.7558< 10.0.19044.6093< 10.0.19045.6093< 10.0.22621.5624< 10.0.22631.5624< 10.0.26100.4652CVSS 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
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:L/AC:L/PR:N/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 checksWork through these to decide whether this CVE applies to you.
-
Check Windows version and build numberOpen Command Prompt or PowerShell and run 'winver' or 'systeminfo | findstr /B /C:"OS Name" /C:"OS Version"' to display the installed Windows version and build number.Affected if The displayed build number is lower than the threshold for your Windows version (1507: 10240.21073, 1607: 14393.8246, 1809: 17763.7558, 21h2: 19044.6093, 22h2: 19045.6093, 11 22h2: 22621.5624, 11 23h2: 22631.5624, 11 24h2: 26100.4652)
-
Confirm Windows Imaging Component presenceVerify that Windows Imaging Component (WIC) is available on the system by checking the component via 'Get-ItemProperty HKLM:\SOFTWARE\Microsoft\Windows\CurrentVersion\Setup\WindowsFeatures\* | Where-Object {$_.Name -like "*Imaging*"}' or by confirming the system is a standard Windows installation.Affected if Windows Imaging Component is present on the system (this is true for most standard Windows installations) and the version check above shows a build number below the patched threshold.
-
Verify build number via PowerShell alternativeRun '([Environment]::OSVersion).Version' or '([System.Environment]::OSVersion.VersionString)' in PowerShell to get the precise version string for comparison.Affected if The returned version string indicates a build number below the applicable threshold listed in the affected versions.
A system is affected if it runs any of the listed Windows versions with a build number lower than the specified threshold for that version, and Windows Imaging Component is present (which is the default configuration for standard Windows installations).
Generated from the published advisory. Verify against your own configuration.
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 · scoped10.0.10240.2107310.0.14393.824610.0.17763.7558
Apply the appropriate Microsoft security update for Windows Imaging Component once released. Organizations should inventory affected Windows systems and deploy patches through their standard update management processes.
Upgrade to the build number >= your affected version's fixed build (see steps). For Windows 10 1507/1607 which are end-of-life, Microsoft may no longer provide updates; consider upgrading to a supported Windows version.
- Press Win+R, type 'winver', and press Enter to check your current Windows version and build number
- Identify which Windows 10 or Windows 11 version and build you are running from the winver output
- Open Settings > Windows Update and click 'Check for updates' to install the latest security updates
- Alternatively, manually download and install the specific security update for this vulnerability from the Microsoft Update Catalog (search for CVE-2025-47980)
- Verify the installation was successful by checking that your build number matches or exceeds: 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.5624 | Windows 11 24h2: 10.0.26100.4652
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation2.0 h
- Testing1.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,744.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-47980 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2025-47980 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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