dbcve.org
IncopyApplication · Adobe

CVE-2025-30327

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
InCopy versions 20.2, 19.5.3 and earlier are affected by an Integer Overflow or Wraparound 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 InCopy contains an integer overflow vulnerability in how it processes certain file data. When a user opens a specially crafted malicious file, the integer overflow can be triggered, potentially allowing the attacker to execute arbitrary code with the privileges of the current user.

MitigationUpdate Adobe InCopy to the latest patched version (20.3 or later for 20.x, or the appropriate patched version for 19.x) to remediate this vulnerability. Users should avoid opening untrusted files until the patch is 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
IncopyApplication
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 Adobe InCopy version
    Open Adobe InCopy, then go to Help > About Adobe InCopy to display the full version number (for example, 20.2.1 or 19.5.0). Alternatively, on Windows you can right-click the InCopy executable in Program Files, select Properties, and view the File version details.
    Affected if The displayed version is less than 19.5.4, or is 20.0 through 20.2.x (any version >= 20.0 but < 20.3).
  2. Confirm InCopy is used to open external files
    Determine whether users in your environment routinely open InCopy documents (.icml, .incx, or legacy .icml/.inq files) from external sources, network shares, or email attachments. Check default file associations and recent document history.
    Affected if Users open .icml or InCopy-specific file types from untrusted sources, which is the attack vector for triggering the integer overflow.
  3. Review recent InCopy file opening activity
    On Windows, check the Windows Event Viewer under Security or Application logs for evidence of InCopy launching files. On macOS, review the unified log for InCopy file open events.
    Affected if InCopy has been used to open any files, particularly from locations outside the organization or from untrusted senders.

You are affected if Adobe InCopy version is less than 19.5.4 or falls between 20.0 and 20.2.x inclusive, and users open external InCopy document 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.3 or later
Fixed in 19.5.420.3
Interim mitigation

Update Adobe InCopy to the latest patched version (20.3 or later for 20.x, or the appropriate patched version for 19.x) to remediate this vulnerability. Users should avoid opening untrusted files until the patch is applied.

Recommended fix High confidence

InCopy 19.5.4 (for 19.x line) or InCopy 20.3 (for 20.x line)

  1. Open Adobe InCopy and navigate to Help > About InCopy to identify your current version number
  2. Close any open documents and back up important InCopy files before upgrading
  3. If using InCopy 19.x (e.g., 19.5.3 or earlier), upgrade to version 19.5.4
  4. If using InCopy 20.x (e.g., 20.0-20.2), upgrade to version 20.3
  5. Download the fixed version from the official Adobe website (helpx.adobe.com) or use Adobe Creative Cloud desktop application to update
  6. Launch the updated InCopy version and verify the version number reflects the patch (19.5.4 or 20.3)
Caveat Upgrading across major version lines may introduce compatibility considerations with documents created in very old versions; test critical documents after upgrade

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

Fix this in Incopy Scoped from the published advisory
  • Consultation4.0 h
  • Implementation4.0 h
  • Testing2.0 h
  • Review / QA2.0 h
12.0 hours of engineering $2,180
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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