dbcve.org
IndesignApplication · Adobe

CVE-2025-30319

MEDIUM · 5.5 CVSS v3.1 Published 2025-05-13
Fix available
A fix is available. Upgrade to 19.5.3 / 20.3 or later.
See remediation →
58/100
Remediation priority · Elevated
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 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 a 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 confidence

A NULL Pointer Dereference vulnerability exists in Adobe InDesign Desktop versions ID19.5.2, ID20.2 and earlier. When a user opens a specially crafted malicious InDesign file, the application attempts to dereference a NULL pointer, causing it to crash and result in denial of service.

MitigationUpdate to the latest Adobe InDesign version when patches become available. Avoid opening InDesign files from untrusted or unknown sources.

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.3>= 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
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 checks

Work through these to decide whether this CVE applies to you.

  1. Locate Adobe InDesign installation
    On Windows, open Control Panel > Programs and Features and find 'Adobe InDesign' in the list. On macOS, open Finder > Applications and locate the Adobe InDesign folder, or run 'system_profiler SPApplicationsDataType | grep -i InDesign' in Terminal.
    Affected if Adobe InDesign is installed on the system
  2. Determine installed InDesign version number
    On Windows, right-click Adobe InDesign in Programs and Features and select Properties to view the Version field. On macOS, right-click Adobe InDesign in Applications, select Get Info, and note the Version number shown.
    Affected if Version cannot be determined or is not displayed
  3. Compare version against affected ranges
    Check if the installed version is either: (1) 19.x and less than 19.5.3, OR (2) 20.x and less than 20.3. For example, versions 19.5.2, 20.0, 20.1, and 20.2 are all affected.
    Affected if Installed version is 19.5.2 or earlier, OR is 20.0 through 20.2 inclusive
  4. Verify InDesign executable version as secondary confirmation
    Navigate to the InDesign installation directory (typically C:\Program Files\Adobe\Adobe InDesign CC 2024 or CC 2025 on Windows, or /Applications/Adobe InDesign CC 2024/2025 on Mac). Right-click the InDesign.exe or InDesign binary, select Properties/Details, and confirm the File Version matches the program version.
    Affected if Executable version differs from the listed program version or cannot be verified

A system is affected if Adobe InDesign is installed with version 19.5.2 or earlier, or version 20.0 through 20.2 inclusive.

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.3 / 20.3 or later
Fixed in 19.5.320.3
Interim mitigation

Update to the latest Adobe InDesign version when patches become available. Avoid opening InDesign files from untrusted or unknown sources.

Recommended fix High confidence

InDesign 19.5.3 or later, or InDesign 20.3 or later

  1. 1. Determine the current InDesign version by opening InDesign and going to Help > About InDesign
  2. 2. If the version is 19.5.2 or earlier (19.x.x), upgrade to version 19.5.3 or later
  3. 3. If the version is 20.0, 20.1, or 20.2, upgrade to version 20.3 or later
  4. 4. Download the updated version from the official Adobe website at get.adobe.com/indesign
  5. 5. Close all running InDesign instances
  6. 6. Run the installer and follow the prompts to complete the upgrade
  7. 7. After installation, verify the new version by checking Help > About InDesign
Caveat Major version upgrades (e.g., 19.x to 20.x) may include UI changes, deprecated features, or file format updates - test critical workflows before deploying broadly

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

Fix this in Indesign Scoped from the published advisory
  • Consultation1.0 h
  • Implementation1.0 h
  • Testing1.0 h
  • Review / QA1.0 h
4.0 hours of engineering $750
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,200.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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