dbcve.org
365 AppsApplication · Microsoft

CVE-2025-54905

HIGH · 7.1 CVSS v3.1 Published 2025-09-09
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
74/100
Remediation priority · Elevated
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
Untrusted pointer dereference in Microsoft Office Word 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 confidence

This is a local information disclosure vulnerability in Microsoft Office Word caused by an untrusted pointer dereference. The vulnerability allows an unauthorized local attacker to read sensitive information from memory due to Word improperly handling a pointer value, potentially exposing data that should not be accessible.

MitigationApply the Microsoft security update for CVE-2025-54905 when available. Until then, exercise caution when opening Word documents from untrusted sources and consider using Protected View or Application Guard for documents from external parties.

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:= 2019
Office Long Term Servicing ChannelApplication
Affected:= 2021= 2024
Sharepoint Enterprise ServerApplication
Affected:= 2016
Sharepoint ServerApplication
Affected:= 2019
WordApplication
Affected:= 2016

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

CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:N/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 Microsoft Word is installed
    Open PowerShell and run: Get-ItemProperty 'HKLM:\SOFTWARE\Microsoft\Windows\CurrentVersion\App Paths\WINWORD.EXE' -ErrorAction SilentlyContinue | Select-Object -ExpandProperty '(default)'. Alternatively, check Start Menu for Word or look in C:\Program Files\Microsoft Office\ or C:\Program Files (x86)\Microsoft Office\
    Affected if WINWORD.EXE is found on the system, indicating Word is installed
  2. Identify the installed Word version
    Open Word, go to File > Account > About Word, or run: winword.exe /? from Command Prompt. For Microsoft 365 or Office 365, check via File > Account > View Updates. For legacy Office, check via Control Panel > Programs and Features > Microsoft Office > Change
    Affected if The version matches: Microsoft 365 (any version), Office 2019, Office 2021, Office 2024 LTSC, Word 2016, or any version of Word that corresponds to these Office releases
  3. Check SharePoint version if Word is part of a SharePoint deployment
    If using SharePoint, check the version via SharePoint Administration Center (/_admin/version.aspx) or run: Get-SPFarm | Select-Object BuildVersion on SharePoint server. For SharePoint 2016 or 2019, Word Web App or related components may be affected
    Affected if SharePoint Server 2016 or 2019 is installed, as these versions bundle affected Word components
  4. Verify if Word processes opened documents in a way that triggers pointer handling
    This vulnerability is triggered by opening a specially crafted Word document. Check recent Word documents from untrusted sources. There is no direct registry or config check; the vulnerability is in how Word handles pointer values during document processing
    Affected if User opens or has opened Word documents from untrusted or external sources, particularly those that could exploit the untrusted pointer dereference

The environment is affected if Microsoft Word (any version including Microsoft 365, Office 2019/2021/2024 LTSC, Word 2016) or SharePoint Server 2016/2019 with Word components is installed, and the user opens a specially crafted document that exploits the untrusted pointer dereference to disclose memory contents.

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.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Apply the Microsoft security update for CVE-2025-54905 when available. Until then, exercise caution when opening Word documents from untrusted sources and consider using Protected View or Application Guard for documents from external parties.

Fix this in 365 Apps Scoped from the published advisory
  • Consultation2.0 h
  • Implementation1.0 h
  • Testing2.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,060
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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