CVE-2025-30320
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 · uneditedInDesign Desktop versions ID19.5.2, ID20.2 and earlier are affected by a NULL Pointer Dereference vulnerability that could lead to application denial-of-service. An attacker could exploit this vulnerability to crash the application, causing disruption in service. Exploitation of this issue requires user interaction in that a victim must open a malicious file.
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 · high confidenceA NULL pointer dereference vulnerability in Adobe InDesign Desktop versions ID19.5.2, ID20.2 and earlier allows an attacker to crash the application by tricking a user into opening a maliciously crafted InDesign file, resulting in denial of service.
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< 19.5.3>= 20.0, < 20.3CVSS 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
- None
- Integrity
- None
- Availability
- High
CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:N/I:N/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.
-
Locate installed InDesign versionOpen Adobe InDesign and go to Help > About InDesign (on Windows) or InDesign > About InDesign (on Mac). The version number displays in the dialog that appears. Alternatively, open Adobe Creative Cloud desktop app, go to the Installed apps section, and find InDesign to see its installed version.Affected if version shown is 19.5.2, 20.2, or any earlier version (below 19.5.3, or 20.0 through 20.2)
-
Confirm version against affected rangeCompare the installed version number to these ranges: versions 19.x below 19.5.3 (such as 19.5.2, 19.5.1, 19.5, 19.4 and earlier), or versions 20.0 through 20.2 (20.2, 20.1, 20.0). Versions 19.5.3 and above, or 20.3 and above, are not affected.Affected if installed version falls within < 19.5.3 or >= 20.0 but < 20.3
User is affected if their installed InDesign Desktop version is older than 19.5.3 (19.x series) or falls between 20.0 and 20.2 (20.x series).
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.
dbcve · scoped19.5.320.3
Apply the vendor security patch from Adobe when available. Until then, instruct users to only open InDesign files from trusted sources and avoid opening unsolicited or unexpected files.
InDesign 19.5.3 or later; InDesign 20.3 or later
- Back up any important InDesign documents and settings before updating
- Close InDesign if it is currently running
- Navigate to the Adobe InDesign official downloads page or use Adobe Creative Cloud desktop application to check for updates
- Download InDesign version 19.5.3 or later (for 19.x line) OR version 20.3 or later (for 20.x line)
- Run the installer and follow the prompts to complete the update
- Restart your computer after installation completes
- Launch InDesign and verify the application starts without errors
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation1.0 h
- Testing1.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,200.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-30320 — 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-30320 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