CVE-2025-30321
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 ID20.2, ID19.5.3 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 confidenceAdobe InDesign Desktop versions ID20.2, ID19.5.3 and earlier contain a NULL pointer dereference vulnerability that can be triggered when a victim opens a specially crafted malicious file. The vulnerability causes the application to crash, resulting in denial-of-service conditions. User interaction is required (opening the malicious file), and there is no indication of code execution capability.
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.4>= 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.
-
Identify installed InDesign versionOpen InDesign and navigate to Help > About InDesign, or right-click the InDesign executable in Program Files and select Properties > Details to view the version numberAffected if Version displays as ID20.2, ID19.5.3, or any earlier version number
-
Compare version against affected rangesReview the version number identified and check if it falls below 19.5.4, or is 20.0 through 20.2 (the versions between 20.0 and 20.3 exclusive)Affected if Installed version is less than 19.5.4, OR is version 20.0, 20.1, or 20.2
-
Verify InDesign is present on the systemSearch for InDesign.exe in common installation paths such as C:\Program Files\Adobe\Adobe InDesign 2024 or C:\Program Files\Adobe\Adobe InDesign 2025, or check Program Files for Adobe InDesign foldersAffected if InDesign software is installed on the system
The environment is affected if Adobe InDesign Desktop version is either below 19.5.4, or falls within the 20.0 to 20.2 range (versions 20.0, 20.1, or 20.2).
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.420.3
Avoid opening untrusted or unexpected InDesign files from unverified sources. Apply vendor-supplied patches or updates when Adobe releases a fix for this vulnerability. Consider implementing file type restrictions and user awareness training to reduce exposure.
InDesign 19.5.4 or later for 19.x branch; InDesign 20.3 or later for 20.x branch
- 1. Close Adobe InDesign if currently running
- 2. Open Adobe Creative Cloud desktop application or navigate to helpx.adobe.com/installation
- 3. Locate Adobe InDesign in your installed applications
- 4. Check current version by opening InDesign and going to Help > About InDesign
- 5. If version is < 19.5.4 or >= 20.0 but < 20.3, initiate update via Creative Cloud or download the fixed version from Adobe's official download page
- 6. Download and install InDesign version 19.5.4 or later (for 19.x branch), or version 20.3 or later (for 20.x branch)
- 7. Restart the application after update completes
- 8. Verify the updated version by checking Help > About InDesign
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation3.0 h
- Implementation6.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 $4,224.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-30321 — 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-30321 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