CVE-2025-53730
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 · uneditedUse after free in Microsoft Office Visio 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 confidenceA use-after-free vulnerability exists in Microsoft Office Visio that allows an unauthorized attacker to execute code locally. The flaw occurs when the software continues to use memory after it has been freed, potentially enabling an attacker to manipulate memory and achieve arbitrary code execution.
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 dataall versions= 2019= 2021= 2024CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Confirm Visio installationOpen Control Panel > Programs and Features, or run 'Get-ItemProperty HKLM:\Software\Microsoft\Windows\CurrentVersion\Uninstall\* | Select-Object DisplayName, DisplayVersion' via PowerShell to list installed programs. Look for 'Microsoft Visio' in the list.Affected if Visio is not installed on the system
-
Identify Visio versionIf Visio is installed, locate its version: right-click the Visio executable (typically in C:\Program Files\Microsoft Office\root\OfficeXX or C:\Program Files (x86)\Microsoft Office\root\OfficeXX), select Properties, and check the Details tab for Version. Alternatively, open Visio, go to File > Account > About Visio.Affected if The detected version does not match any of the affected versions: Office 2019, Office LTSC 2021, Office LTSC 2024, or any Microsoft 365 Apps version
-
Determine Office subscription typeOpen any Office app (such as Word or Excel), go to File > Account, and check whether it shows 'Microsoft 365' or a version number. If it shows Microsoft 365, it falls under the 'Microsoft 365 Apps: all versions' affected range.Affected if The installation is Microsoft 365 Apps and the Visio component is present
-
Check for pending security updatesOpen Windows Settings > Update & Security > Windows Update, click 'Check for updates,' and review whether any Microsoft Office security updates for CVE-2025-53730 are available but not yet installed.Affected if Security updates for this CVE are available but have not been applied
You are affected if Visio is installed and its version corresponds to Office 2019, Office LTSC 2021, Office LTSC 2024, or Microsoft 365 Apps (any version), and the CVE-2025-53730 security update has not been applied.
Generated from the published advisory. Verify against your own configuration.
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 dataApply the Microsoft security update for CVE-2025-53730 through Windows Update or enterprise patch management systems. Test Visio functionality in a non-production environment before deploying organization-wide.
- Consultation2.0 h
- Implementation4.0 h
- Testing4.0 h
- Review / QA2.0 h
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 locallyCheck whether your project pulls in CVE-2025-53730 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2025-53730 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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