dbcve.org
365 AppsApplication · Microsoft

CVE-2025-53733

HIGH · 8.4 CVSS v3.1 Published 2025-08-12
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
89/100
Remediation priority · High
No privileges Zero-click

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
Incorrect conversion between numeric types 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 confidence

This is a type confusion vulnerability in Microsoft Office Word where incorrect conversion between numeric types allows a local attacker to execute arbitrary code. The vulnerability has a high CVSS score of 8.4, indicating significant impact potential.

MitigationApply available Microsoft security updates for Office Word immediately; given the high severity and local code execution capability, prioritize rapid patching across all affected endpoints.

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

CVSS:3.1/AV:L/AC:L/PR:N/UI:N/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. Locate the Word executable
    Find WINWORD.EXE on the system. Typical paths: C:\Program Files\Microsoft Office\root\Office16\WINWORD.EXE or C:\Program Files (x86)\Microsoft Office\root\Office16\WINWORD.EXE. Use PowerShell: Get-ChildItem -Path 'C:\Program Files','C:\Program Files (x86)' -Filter 'WINWORD.exe' -Recurse -ErrorAction SilentlyContinue
    Affected if File is not found, meaning Word is not installed (not affected). If found, proceed to next step.
  2. Get the installed Word version
    Right-click WINWORD.exe, select Properties, then Details tab. Or use PowerShell: (Get-Item 'C:\Program Files\Microsoft Office\root\Office16\WINWORD.exe').VersionInfo.FileVersion
    Affected if Version information is unavailable (not affected). If available, proceed to next step.
  3. Identify the Office/Word release version
    Check the major version number from the file version obtained. Microsoft Office 2016 typically shows version 16.x, Office 2019 shows 16.x as well but is identified by the license type. Microsoft 365 Apps show as version 16.x with ongoing updates. Check registry: HKLM\SOFTWARE\Microsoft\Office\ClickToRun\Configuration or HKLM\SOFTWARE\Microsoft\Office\16.0\Common\InstallRoot for the exact version string.
    Affected if Unable to determine release version from registry or file (not affected). If determined, proceed to next step.
  4. Compare against affected versions
    The CVE affects: Microsoft 365 Apps (all versions), Office 2019, Office LTSC 2021, Office LTSC 2024, SharePoint Enterprise Server 2016, SharePoint Server 2019, and Word 2016. Match your identified version against this list. Note: This is a type confusion flaw in numeric type conversion during document processing, meaning any document parsing operation in affected Word versions could trigger it.
    Affected if Your installed Word/Office version matches one of the affected versions listed in the CVE (affected). If it does not match, you are likely not affected.

A user is affected if they have Microsoft Word installed with a version matching Office 2016, Office 2019, Office LTSC 2021, Office LTSC 2024, or Microsoft 365 Apps, as all these versions contain the vulnerable numeric type conversion code in the document parsing component.

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 available Microsoft security updates for Office Word immediately; given the high severity and local code execution capability, prioritize rapid patching across all affected endpoints.

Fix this in 365 Apps Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,490
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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