dbcve.org
365 AppsApplication · Microsoft

CVE-2025-24083

HIGH · 7.8 CVSS v3.1 Published 2025-03-11
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
Untrusted pointer dereference in Microsoft Office 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

CVE-2025-24083 is an untrusted pointer dereference vulnerability in Microsoft Office that allows an unauthenticated attacker to execute arbitrary code locally on the target system. The vulnerability stems from improper validation of pointer references during Office document processing, which can be triggered by opening a specially crafted malicious Office file.

MitigationApply Microsoft security patches for CVE-2025-24083 immediately upon release. Until the patch is available, exercise caution with untrusted Office documents and consider disabling macros and OLE objects via Group Policy or Office Trust Center settings.

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

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 Microsoft Office product and version
    Open any Office application (Word, Excel, PowerPoint), go to File > Account > About [AppName] to view the version number. Alternatively, run 'Get-ItemProperty HKLM:\SOFTWARE\Microsoft\Office\ClickToRun\Configuration -ErrorAction SilentlyContinue | Select-Object PlatformVersion,VersionToReport' in PowerShell for Click-to-Run installations, or check 'Get-ItemProperty HKLM:\SOFTWARE\Microsoft\Office\*\Common\InstallRoot -ErrorAction SilentlyContinue' for MSI installations.
    Affected if The installed version matches Microsoft 365 Apps (any version), Office 2016, Office 2019, Office LTSC 2021, or Office LTSC 2024.
  2. Confirm Office document processing is active
    Check if Office applications are configured to open documents by default. Verify the presence of Office file handlers (.docx, .xlsx, .pptx) in the system registry under HKCR:\.docx\OpenWithProgids and similar keys, or check that Office applications launch without errors.
    Affected if Office applications are installed and capable of opening document files, making the vulnerability path viable.
  3. Verify macro and OLE object execution settings
    Open any Office application, go to File > Options > Trust Center > Trust Center Settings > Macro Settings or OLE Object Settings. Check whether macros can run or OLE objects can be inserted without user notification.
    Affected if Settings allow automatic or low-restriction execution of macros or OLE objects, which could amplify the impact of the pointer dereference flaw when a malicious file is opened.
  4. Check for recent Office security updates
    Open any Office application, go to File > Account > Update Options > View Update History. Look for any updates installed around the CVE disclosure date. Alternatively, check Windows Update history for installed Office security patches.
    Affected if No security update addressing CVE-2025-24083 has been installed, leaving the vulnerability unpatched.

If Microsoft Office (version 2016, 2019, 2021, 2024, or Microsoft 365 Apps) is installed without the CVE-2025-24083 security patch, the system is vulnerable when processing untrusted Office documents.

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 Microsoft security patches for CVE-2025-24083 immediately upon release. Until the patch is available, exercise caution with untrusted Office documents and consider disabling macros and OLE objects via Group Policy or Office Trust Center settings.

Fix this in 365 Apps Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA1.0 h
10.0 hours of engineering $1,750
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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