dbcve.org
365 AppsApplication · Microsoft

CVE-2025-30375

HIGH · 7.8 CVSS v3.1 Published 2025-05-13
Fix available
A fix is available. Upgrade to 16.0.10417.20010 or later.
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
Access of resource using incompatible type ('type confusion') in Microsoft Office Excel 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

Type confusion vulnerability in Microsoft Office Excel allows an attacker to execute code locally. The vulnerability involves accessing a resource using an incompatible type, which can be leveraged to achieve code execution on the affected system.

MitigationApply Microsoft security updates for Excel as they become available through standard patch management processes. Prioritize updates on systems running affected Excel versions.

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
ExcelApplication
Affected:= 2016
OfficeApplication
Affected:= 2019
Office Long Term Servicing ChannelApplication
Affected:= 2021= 2024
Office Online ServerApplication
Affected:< 16.0.10417.20010

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. Confirm Microsoft Excel is installed
    Open Registry Editor and navigate to HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\App Paths\EXCEL.EXE, or check for the existence of typical Excel executable paths such as C:\Program Files\Microsoft Office\root\Office16\EXCEL.EXE or C:\Program Files (x86)\Microsoft Office\root\Office16\EXCEL.EXE
    Affected if Excel is not installed on the system (not affected)
  2. Determine installed Excel version via registry
    Open Registry Editor and check HKEY_CLASSES_ROOT\Excel.Application\CurVer for the class version, then look up the corresponding version in HKEY_CLASSES_ROOT\Excel.Application.<version>\DefaultIcon to confirm the install location. Alternatively, check HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Office\ClickToRun\Configuration for Microsoft 365 Apps version, or HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Office\<version>\Excel\InstallRoot for traditional Office installs
    Affected if Cannot determine version from registry (verification inconclusive)
  3. Determine Office Online Server version
    On the Office Online Server, open the SharePoint Management Shell and run Get-OfficeWebAppsFarm to retrieve the Farm version, or check the installed program version in Programs and Features for Office Online Server
    Affected if Office Online Server version is 16.0.10417.20010 or higher (not affected)
  4. Compare version against affected ranges
    Cross-reference the detected version with the following ranges: Microsoft 365 Apps (all versions affected), Excel 2016 and later, Office 2019 and later, Office LTSC 2021 and 2024, Office Online Server versions before 16.0.10417.20010
    Affected if The installed version falls within: Excel >= 2016, Office >= 2019, Office LTSC 2021 or 2024, or Office Online Server < 16.0.10417.20010

You are affected if Microsoft Excel or Office with Excel is installed and the version matches the affected ranges (all Microsoft 365 Apps versions, Excel 2016+, Office 2019+, Office LTSC 2021/2024, or Office Online Server < 16.0.10417.20010).

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
Upgrade available Upgrade to 16.0.10417.20010 or later
Fixed in 16.0.10417.20010
Interim mitigation

Apply Microsoft security updates for Excel as they become available through standard patch management processes. Prioritize updates on systems running affected Excel versions.

Recommended fix Moderate confidence

Apply Microsoft security updates for CVE-2025-30375; for Office Online Server upgrade to 16.0.10417.20010 or higher

  1. Check Microsoft Security Response Center (msrc.microsoft.com) for CVE-2025-30375 security bulletin and the specific patch/KB article for your product
  2. For Office Online Server: upgrade to version 16.0.10417.20010 or later
  3. For Microsoft 365 Apps, Excel 2016, Office 2019, Office 2021, and Office 2024: apply the corresponding Microsoft security update referenced in the CVE bulletin
  4. Verify the patch has been applied by checking installed updates or using the Office Update History
Caveat Standard Microsoft patch deployment; review KB article for any known issues before production deployment

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
  • Testing3.0 h
  • Review / QA1.0 h
7.0 hours of engineering $1,190
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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