dbcve.org
IndesignApplication · Adobe

CVE-2025-30317

HIGH · 7.8 CVSS v3.1 Published 2025-06-10
Fix available
A fix is available. Upgrade to 19.5.4 / 20.3 or later.
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
InDesign Desktop versions ID20.2, ID19.5.3 and earlier are affected by a Heap-based Buffer Overflow vulnerability that could result in arbitrary code execution in the context of the current user. 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 confidence

A heap-based buffer overflow vulnerability exists in Adobe InDesign Desktop versions ID20.2, ID19.5.3 and earlier. When a user opens a specially crafted malicious .indd file, the overflow allows arbitrary code execution in the context of the current user's privileges.

MitigationUpdate InDesign to version ID20.3 or later (for ID20.x) and ID19.5.4 or later (for ID19.x). Avoid opening .indd files from untrusted or unknown sources until patches are applied.

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
IndesignApplication
Affected:< 19.5.4>= 20.0, < 20.3

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. Check installed InDesign version on Windows
    Open InDesign, go to Help menu, select About InDesign. The version number displays in the dialog. Alternatively, check the Windows Registry key: HKEY_LOCAL_MACHINE\SOFTWARE\Adobe\InDesign\InstallVersion
    Affected if Version shown is ID19.5.3 or earlier, OR ID20.0 through ID20.2 (i.e., < 19.5.4, or >= 20.0 and < 20.3)
  2. Check installed InDesign version on macOS
    Open InDesign, go to InDesign menu, select About InDesign. The version number displays in the dialog. Alternatively, check /Applications/Adobe InDesign [version]/Contents/Info.plist for CFBundleShortVersionString
    Affected if Version shown is ID19.5.3 or earlier, OR ID20.0 through ID20.2 (i.e., < 19.5.4, or >= 20.0 and < 20.3)
  3. Verify if .indd files have been opened from untrusted sources
    Review recent file history or check for unknown .indd files in your Recent Files list or Downloads folder. If you have opened .indd files from email attachments, external drives, or unverified websites, potential exposure exists
    Affected if You have opened .indd files from untrusted or unknown sources while running an affected version

You are affected if your installed InDesign version is ID19.5.3 or earlier, or ID20.0 through ID20.2, and you have opened .indd files from untrusted sources.

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
Upgrade available Upgrade to 19.5.4 / 20.3 or later
Fixed in 19.5.420.3
Interim mitigation

Update InDesign to version ID20.3 or later (for ID20.x) and ID19.5.4 or later (for ID19.x). Avoid opening .indd files from untrusted or unknown sources until patches are applied.

Recommended fix High confidence

InDesign 19.5.4 (2024 release) or InDesign 20.3 (2025 release)

  1. 1. Close all running instances of Adobe InDesign
  2. 2. Open Adobe Creative Cloud desktop application or navigate to helpx.adobe.com
  3. 3. Locate Adobe InDesign in your installed applications
  4. 4. Check for available updates - look for version 19.5.4 or higher for InDesign 2024, or version 20.3 or higher for InDesign 2025
  5. 5. Click Update to download and install the latest version
  6. 6. Alternatively, download the installer directly from helpx.adobe.com by searching for the InDesign version update
  7. 7. Restart your computer after installation completes
  8. 8. Verify the installed version by opening InDesign and checking Help > About InDesign
Caveat Standard update - review Adobe release notes for minor feature changes between versions

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Indesign Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
7.0 hours of engineering $1,240
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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