dbcve.org
365 AppsApplication · Microsoft

CVE-2025-49705

HIGH · 7.8 CVSS v3.1 Published 2025-07-08
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
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
Heap-based buffer overflow in Microsoft Office PowerPoint 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

Heap-based buffer overflow vulnerability in Microsoft Office PowerPoint that allows an unauthorized local attacker to execute arbitrary code. This is a memory corruption vulnerability typically triggered by parsing a specially crafted PowerPoint file.

MitigationApply Microsoft security updates for Office/PowerPoint or upgrade to a patched version. Consider disabling macros and restricting PowerPoint file handling from untrusted sources until patches are applied.

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
PowerpointApplication
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
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. Identify installed PowerPoint version
    Open PowerPoint, go to File > Account > About PowerPoint, or run `winword.exe /?` from Command Prompt to check the version, or check the registry at HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Office\ClickToRun\Configuration for Microsoft 365/Office installations
    Affected if The installed version matches one of the affected versions: Microsoft 365 Apps (all versions), Office 2019, Office LTSC 2021, Office LTSC 2024, or PowerPoint 2016
  2. Confirm PowerPoint application is present
    Check for the presence of POWERPNT.exe in typical installation paths such as C:\Program Files\Microsoft Office\root\Office16\ or C:\Program Files (x86)\Microsoft Office\root\Office16\
    Affected if PowerPoint executable exists on the system, indicating the application is installed and potentially vulnerable
  3. Check Office update installation status
    Open any Office app, go to File > Account > Update Options > View Update History, or check Windows Update history for recent Office security updates
    Affected if No relevant security updates for CVE-2025-49705 have been installed, or the installed version remains within the affected version ranges

A user is affected if they have any of the listed PowerPoint/Office versions installed and the corresponding security patch for CVE-2025-49705 has not been applied.

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
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Apply Microsoft security updates for Office/PowerPoint or upgrade to a patched version. Consider disabling macros and restricting PowerPoint file handling from untrusted sources until patches are applied.

Recommended fix Moderate confidence

Microsoft 365 Apps (current channel) or Office 2024

  1. Open PowerPoint and go to File > Account to verify the current Office version
  2. For Microsoft 365 Apps users: Go to File > Account > Update Options > Update Now to install the latest security updates
  3. For standalone Office users: Visit the Microsoft Update Catalog (catalog.update.microsoft.com) and search for the latest Office security updates
  4. Alternatively, ensure Windows Update is enabled and configured to automatically install Microsoft updates
  5. After updating, verify the Office version has been updated to confirm the patch was applied
  6. If running unsupported Office versions (e.g., Office 2016 which has reached end of support), upgrade to a supported version such as Microsoft 365 Apps or Office 2024
Caveat Ensure compatibility with existing add-ins and macros before updating; some legacy features may be deprecated in newer versions

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
  • Testing1.0 h
  • Review / QA1.0 h
5.0 hours of engineering $890
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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