CVE-2025-62559
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 · uneditedUse after free in Microsoft Office Word 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 confidenceA use-after-free vulnerability in Microsoft Office Word allows an attacker to execute arbitrary code locally through specially crafted Word documents. The vulnerability stems from improper memory management where memory is accessed after being freed, potentially leading to controlled code execution.
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 dataall versions= 2019= 2021= 2024= 2016= 2019= 2016CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Verify Microsoft Word is installedCheck for the presence of WINWORD.exe in typical Office installation paths such as C:\Program Files\Microsoft Office\root\Office16\ or C:\Program Files (x86)\Microsoft Office\root\Office16\, or search for WINWORD.exe using PowerShell: Get-ChildItem -Path 'C:\Program Files', 'C:\Program Files (x86)' -Filter 'WINWORD.exe' -Recurse -ErrorAction SilentlyContinueAffected if WINWORD.exe is found on the system, indicating Microsoft Word is installed
-
Determine the installed Microsoft Word or Office versionOpen Word and go to File > Account > About Word to view the version number, or check the Windows Registry at HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Office\ClickToRun\Configuration or HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Office\16.0\Common\InstallRoot for the version stringAffected if The installed version matches or falls within: Microsoft 365 Apps (all versions), Office 2019, Office LTSC 2021, Office LTSC 2024, Word 2016, SharePoint Server 2016, or SharePoint Server 2019
-
Identify Microsoft SharePoint Server installationCheck Windows Services for 'SharePoint' services running, or check registry at HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Shared Tools\Web Server Extensions\ for version 15.0 (2016) or 16.0 (2019), or inspect Program Files for SharePoint installation directoriesAffected if SharePoint Server 2016 or 2019 is installed and running on the server
-
Confirm the exact version build numberRun 'winword.exe /?' from command prompt to display version information, or within Word go to File > Account > About Word and record the full build number (for example: 16.0.xxxxx.xxxxx)Affected if The build number corresponds to an unpatched version within the affected product versions listed
If Microsoft Word, Microsoft Office 2019/2021/2024, Microsoft 365 Apps with Word, or SharePoint Server 2016/2019 is installed without the corresponding security update for CVE-2025-62559, the environment is affected by this use-after-free vulnerability.
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.
From vendor dataApply the relevant Microsoft security update for Microsoft Office Word when released; users should avoid opening untrusted or unexpected Word documents until the patch is applied.
- Consultation2.0 h
- Implementation4.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,088.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-62559 — 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-62559 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