dbcve.org
365 AppsApplication · Microsoft

CVE-2025-47175

HIGH · 7.8 CVSS v3.1 Published 2025-06-10
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
Use after free 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

A use-after-free vulnerability exists in Microsoft Office PowerPoint where memory is accessed after it has been freed, allowing an attacker to execute arbitrary code locally on the affected system.

MitigationApply Microsoft security updates for Office when available. Until then, restrict local user privileges and avoid opening untrusted PowerPoint files from unknown sources.

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. Verify PowerPoint is installed
    Check for PowerPoint in the Windows Start menu, or look for PowerPoint.exe in Program Files or Program Files (x86) folders. Also check Add/Remove Programs or Settings > Apps.
    Affected if PowerPoint is not installed on the system - no further action needed
  2. Identify the installed PowerPoint version
    Open PowerPoint, go to File > Account, and click About PowerPoint. Alternatively, right-click the PowerPoint.exe file in Program Files, select Properties, and check the Details tab for the version number.
    Affected if The displayed version matches the affected versions: Microsoft 365 Apps (any), Office 2019, Office LTSC 2021, Office LTSC 2024, or PowerPoint 2016
  3. Confirm the specific Office installation type
    Run 'winver' from the command prompt to see the Windows and Office version details, or open any Office app, go to File > Account > About [App] to see the full version string including channel information (Monthly, Semi-Annual, LTSC).
    Affected if Office is installed as a subscription (Microsoft 365) or as one of the specific LTSC/retail versions known to be affected
  4. Determine if the vulnerability can be triggered
    The vulnerability is triggered when opening a specially crafted PowerPoint file (.pptx). There is no registry or config check that reveals if the flaw is present - it is a memory corruption issue in the PowerPoint file parsing logic.
    Affected if PowerPoint is installed and running an affected version - the vulnerability exists regardless of configuration and only manifests when a malicious file is opened

If Microsoft PowerPoint is installed and the version matches Microsoft 365 Apps (any), Office 2019, Office LTSC 2021, Office LTSC 2024, or PowerPoint 2016, the environment is potentially affected and the system is vulnerable when opening untrusted PowerPoint 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
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Apply Microsoft security updates for Office when available. Until then, restrict local user privileges and avoid opening untrusted PowerPoint files from unknown sources.

Recommended fix Moderate confidence

Microsoft 365 Apps (current channel) or Office LTSC 2024

  1. Ensure Microsoft 365 Apps are updated to the latest version via automatic updates or by opening any Office app and going to File > Account > Update Options > Update Now
  2. For Office LTSC 2024, verify Windows Update has installed the latest Office patches, or manually check for updates via File > Account > Update Options > Update Now
  3. For Office LTSC 2021 and Office 2019, apply the latest security updates from Windows Update or the Microsoft Update Catalog
  4. For PowerPoint 2016, note that this version is no longer supported; migrate to a supported Office version such as Microsoft 365 Apps or Office LTSC 2024
  5. After updating, restart PowerPoint and verify the application launches without errors
Caveat Ensure compatibility with existing add-ins and macros before deploying organization-wide; test in pilot group first

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
  • Testing4.0 h
  • Review / QA2.0 h
12.0 hours of engineering $2,080
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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