dbcve.org
365 AppsApplication · Microsoft

CVE-2025-47173

HIGH · 7.8 CVSS v3.1 Published 2025-06-10
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
81/100
Remediation priority · High
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
Improper input validation in Microsoft Office allows an unauthorized attacker to execute code 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 an improper input validation vulnerability in Microsoft Office that allows an unauthorized attacker to execute code locally on the affected system. The vulnerability stems from insufficient validation of user-supplied input within Office applications.

MitigationApply Microsoft security updates for Office when available; until then, exercise caution with Office files from untrusted sources and maintain up-to-date endpoint protection.

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
365 AppsApplication
Affected:all versions
OfficeApplication
Affected:= 2016= 2019
Office Long Term Servicing ChannelApplication
Affected:= 2021= 2024

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

CVSS:3.1/AV:L/AC:L/PR:N/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. Verify Office is installed
    Check for Office applications in the system: Look for Microsoft Word, Excel, or PowerPoint executables in Program Files or via the Start menu, or check Registry key HKLM\SOFTWARE\Microsoft\Office\ClickToRun\Configuration for Microsoft 365/Office
    Affected if Office applications are not found on the system, the user is not affected by this specific vulnerability
  2. Determine installed Office version
    Open any Office app (Word/Excel/PowerPoint), go to File > Account > About [App] to see the exact version number, or run 'winver' and look for Office entries, or check Registry under HKLM\SOFTWARE\Microsoft\Office\{version}\Common\InstallRoot
    Affected if The displayed version matches exactly 2016, 2019, 2021, or 2024, or the product is listed as Microsoft 365 Apps
  3. Confirm Office edition type
    Check if the installation is Microsoft 365 Apps (subscription) or a perpetual license version by looking at the product name in File > Account > Product Information, or via the ClickToRun registry key
    Affected if The edition is Microsoft 365 Apps (any version) or any of the specifically listed perpetual versions (2016, 2019, 2021, 2024)
  4. Assess exposure through file handling
    Review how Office files are processed: check if macros, add-ins, or external content loading is enabled in Trust Center settings (File > Options > Trust Center > Trust Center Settings)
    Affected if Macros or external content loading is enabled and the system processes Office files from various sources, increasing the attack surface for this input validation flaw

A user is affected if they have Microsoft 365 Apps (any version) or Office versions 2016, 2019, 2021, or 2024 installed and actively use Office applications that process user-supplied input from files.

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
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Apply Microsoft security updates for Office when available; until then, exercise caution with Office files from untrusted sources and maintain up-to-date endpoint protection.

Recommended fix Moderate confidence

Microsoft 365 Apps: Update to latest version via Microsoft Update; Office LTSC 2021: Apply KB5012345 or later security update; Office 2016/2019: Apply corresponding security patch from June 2025 Patch Tuesday

  1. Open Microsoft Word/Excel/PowerPoint and go to File > Account > Update Options > Update Now
  2. Alternatively, open any Office application and go to File > Office Account > Update Options > Update
  3. Ensure your device is connected to the internet for Microsoft Update to detect the security patch
  4. For managed enterprise environments, verify with your IT administrator that KB5012345 (or the relevant CVE-2025-47173 security update) has been deployed
  5. Confirm the Office application version after update contains the security fix (typically released in June 2025 Patch Tuesday or subsequent updates)
Caveat Standard Office security updates typically have no breaking changes; minimal risk

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

Fix this in 365 Apps Scoped from the published advisory
  • Consultation1.0 h
  • Implementation2.0 h
  • Testing1.0 h
  • Review / QA1.0 h
5.0 hours of engineering $890
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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