dbcve.org
365 AppsApplication · Microsoft

CVE-2025-30379

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
Release of invalid pointer or reference 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

A use-after-free vulnerability (release of invalid pointer or reference) in Microsoft Office Excel allows an attacker to execute arbitrary code locally by crafting a malicious Excel file that triggers the memory corruption when opened.

MitigationApply the Microsoft security update for Excel (KB5002772 or subsequent updates) to all affected Office installations; validate through enterprise patch management systems and verify Excel functionality post-patch.

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. Check installed Excel version
    Open Excel, go to File > Account > About Excel. Alternatively, right-click excel.exe in Program Files/Microsoft Office and select Properties > Details to view the File Version.
    Affected if The version shows 2016, 2019, 2021, 2024, or a Microsoft 365/Office 365 version (all of which are affected)
  2. Check Windows Office installation version
    Open Command Prompt and run: msiexec /q /i "{XXXXXXXX-XXXX-XXXX-XXXX-XXXXXXXXXXXX}" / lv* %TEMP%\office_install.log then search the log for ProductVersion. Or open Registry Editor and navigate to HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Office\ClickToRun\Configuration or HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Office\16.0\Common\InstallRoot for version info.
    Affected if The installed Office version is 2016 or higher, 2019 or higher, LTSC 2021, LTSC 2024, or Microsoft 365 Apps (all affected)
  3. Check Office Online Server build number
    On the Office Online Server, open SharePoint Management Shell and run: Get-OfficeWebAppsServer | Select-Object Version. Alternatively, check the build in Programs and Features or the setup.exe version in the installation directory.
    Affected if The build number is less than 16.0.10417.20010 (affected); builds at or above this version are not affected
  4. Confirm vulnerability trigger condition
    The flaw is triggered when a user opens a crafted malicious Excel file (.xlsx, .xls, .xlsm). No specific Excel feature or add-in needs to be enabled; the vulnerability is in the core Excel file parsing logic.
    Affected if Any user who opens an untrusted Excel file from external sources is potentially affected if their Excel version is in the affected range

Your environment is affected if Excel or Office is installed with version 2016 or later (including Microsoft 365 Apps), or Office Online Server is below build 16.0.10417.20010, and users may open untrusted Excel 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
Upgrade available Upgrade to 16.0.10417.20010 or later
Fixed in 16.0.10417.20010
Interim mitigation

Apply the Microsoft security update for Excel (KB5002772 or subsequent updates) to all affected Office installations; validate through enterprise patch management systems and verify Excel functionality post-patch.

Recommended fix Moderate confidence

Apply May 2025 Microsoft Office security update (KB number varies by product); Office Online Server: 16.0.10417.20010

  1. Open Microsoft Excel or any Office application
  2. Go to File > Account > Update Options
  3. Click on 'Update Now' to check for and install the latest Microsoft updates
  4. Alternatively, navigate to Microsoft Update Catalog (catalog.update.microsoft.com) and search for CVE-2025-30379 or the corresponding May 2025 Office security update
  5. Download and install the appropriate security update for your Office version
  6. Restart all Office applications after the update completes
  7. Verify the update was installed by going to File > Account > Update History
Caveat Standard Office security update with no expected breaking changes; may require restart

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

Fix this in 365 Apps Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing2.0 h
  • Review / QA1.0 h
9.0 hours of engineering $1,600
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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