CVE-2025-47107
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 · uneditedInCopy versions 20.2, 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 confidenceA heap-based buffer overflow vulnerability exists in Adobe InCopy versions 20.2, 19.5.3 and earlier. When a user opens a maliciously crafted file, the overflow allows an attacker to execute arbitrary code in the context of the current user session.
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
- 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 checksWork through these to decide whether this CVE applies to you.
-
Verify Adobe InCopy installationCheck for InCopy installation by searching for 'InCopy.exe' in common program directories or using system inventory tools like 'wmic product get name,version' or checking registry under HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\UninstallAffected if Adobe InCopy is not found on the system - the CVE does not apply
-
Locate InCopy executableFind InCopy executable (typically InCopy.exe) in Program Files or Program Files (x86) folders, or use 'where InCopy.exe' command if in PATHAffected if InCopy executable exists - proceed to version check
-
Retrieve installed versionRight-click InCopy.exe, select Properties, then Details tab to view File Version; or use command 'wmic datafile where name="C:\Program Files\Adobe\Adobe InCopy CC 2024\InCopy.exe" get Version' adjusting path as neededAffected if Version number cannot be determined - assume potentially affected if installed
-
Compare version against affected rangesCheck if version is less than 19.5.4, or falls between 20.0 and 20.3 (including 20.2). For example: 19.5.3, 19.5, 20.0, 20.1, 20.2 are all affectedAffected if Version is < 19.5.4 OR (version >= 20.0 AND version < 20.3) - system is vulnerable
-
Confirm file handling contextThis vulnerability triggers when opening a maliciously crafted file. Check if InCopy is configured to open files from untrusted sources or if users have permission to open external filesAffected if Users can open unsolicited files from unknown or untrusted sources - exploitation pathway exists
System is affected by CVE-2025-47107 if Adobe InCopy is installed with a version less than 19.5.4, or version 20.0 through 20.3 inclusive, and users can open files from untrusted sources.
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
Update Adobe InCopy to the latest patched version as released by Adobe. Avoid opening untrusted or unsolicited files from unknown sources.
InCopy 19.5.4 or 20.3 (depending on your licensing branch)
- 1. Close all running instances of Adobe InCopy
- 2. Open Adobe Creative Cloud desktop application on your system
- 3. Navigate to the 'Apps' or 'Updates' section in Creative Cloud
- 4. Find Adobe InCopy in the list of installed applications
- 5. Click the 'Update' button next to InCopy to install the available update
- 6. Alternatively, visit helpx.adobe.com and navigate to the InCopy download or update page
- 7. Download and install InCopy version 19.5.4 (for 19.x branch) or version 20.3 (for 20.x branch)
- 8. After installation, verify the version by opening InCopy and checking Help > About InCopy
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation2.0 h
- Testing1.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,744.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-47107 — 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-47107 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