dbcve.org
IndesignApplication · Adobe

CVE-2025-47103

HIGH · 7.8 CVSS v3.1 Published 2025-07-08
Fix available
A fix is available. Upgrade to 19.5.4 / 20.4 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 19.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

Adobe InDesign Desktop versions 19.5.3 and earlier contain a heap-based buffer overflow vulnerability that can be triggered by opening a maliciously crafted file. Successful exploitation allows arbitrary code execution in the context of the current user, requiring only that the victim open the file.

MitigationUpdate to a patched version of InDesign once released by Adobe. Avoid opening untrusted .indd files from 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.4>= 20.0, < 20.4

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. Verify Adobe InDesign is installed
    Open Windows Settings > Apps > Installed apps, or check Program Files/Adobe folder for InDesign installation directory
    Affected if Adobe InDesign Desktop is present on the system
  2. Find the installed InDesign version number
    Right-click the InDesign shortcut and select Properties, then look at the Details tab for the Product version; alternatively, open InDesign and go to Help > About Adobe InDesign
    Affected if A version number is displayed that can be compared to the affected ranges
  3. Compare version against affected ranges
    Check if the installed version is less than 19.5.4, or between 20.0 and 20.4 (excluding 20.4)
    Affected if Version is < 19.5.4 OR (version >= 20.0 AND version < 20.4)
  4. Identify file-opening trigger condition
    Note that the vulnerability is triggered by opening a crafted .indd file - the affected condition exists if untrusted files can be opened
    Affected if Users can open .indd files from untrusted sources without validation

User is affected if Adobe InDesign is installed with a version less than 19.5.4, or between 20.0 and 20.4, and can open potentially malicious .indd files.

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.4 or later
Fixed in 19.5.420.4
Interim mitigation

Update to a patched version of InDesign once released by Adobe. Avoid opening untrusted .indd files from unknown sources.

Recommended fix High confidence

InDesign 19.5.4+ or 20.4+ (select based on your current major version)

  1. Open Adobe InDesign and go to Help > About Adobe InDesign to check your current version number
  2. Close InDesign completely before updating
  3. Open Adobe Creative Cloud desktop app and navigate to the Apps tab
  4. Find Adobe InDesign in your installed apps list
  5. Click the Update button next to InDesign if an update is available
  6. Alternatively, visit helpx.adobe.com and search for InDesign security updates to manually download the fixed version
  7. Install version 19.5.4 or later for InDesign 19.x, or version 20.4 or later for InDesign 20.x
  8. Restart your computer after the update completes
Caveat Point releases typically have minimal breaking changes; however, test critical workflows after upgrading

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

Fix this in Indesign Scoped from the published advisory
  • Consultation2.0 h
  • Implementation1.0 h
  • Testing2.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,060
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,696.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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