dbcve.org
FramemakerApplication · Adobe

CVE-2025-47122

HIGH · 7.8 CVSS v3.1 Published 2025-07-08
Fix available
A fix is available. Upgrade to 2020.9 / 2022.7 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
Adobe Framemaker versions 2020.8, 2022.6 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 Framemaker versions 2020.8, 2022.6 and earlier contain a heap-based buffer overflow vulnerability that can be triggered when a user opens a malicious file, potentially allowing arbitrary code execution in the context of the current user.

MitigationUpdate Adobe Framemaker to a patched version when released by Adobe, and avoid opening untrusted or unexpected files until the update 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
FramemakerApplication
Affected:< 2020.9>= 2022, < 2022.7

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. Locate Adobe Framemaker installation
    Open Windows Control Panel > Programs and Features, or run 'Get-ItemProperty HKLM:\Software\Microsoft\Windows\CurrentVersion\Uninstall\* | Select-Object DisplayName, DisplayVersion' in PowerShell to list installed Adobe Framemaker versions
    Affected if Adobe Framemaker is listed in installed programs
  2. Identify the exact version number
    If listed in Programs and Features, note the version column. If not, open Framemaker and go to Help > About Adobe Framemaker to see the precise version number (for example, 2020.8, 2022.6, or 2022.7)
    Affected if The displayed version matches a vulnerable release (< 2020.9 or >= 2022 but < 2022.7)
  3. Confirm file handling is enabled
    Verify the application has not been configured to disable file opening. By default, Framemaker can open .fm and .book files. Check if the application launches and allows file operations
    Affected if The application can open files, which is the default behavior required to trigger the vulnerability

A user is affected if Adobe Framemaker version 2020.8 or earlier, or version 2022.6 or earlier (but after 2022.0), is installed and the application retains its ability to open 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 2020.9 / 2022.7 or later
Fixed in 2020.92022.7
Interim mitigation

Update Adobe Framemaker to a patched version when released by Adobe, and avoid opening untrusted or unexpected files until the update is applied.

Recommended fix High confidence

Adobe Framemaker 2020.9 or later, or Adobe Framemaker 2022.7 or later (or latest available release)

  1. 1. Close Adobe Framemaker if it is currently running
  2. 2. Navigate to the Adobe Framemaker download page or open Adobe Creative Cloud desktop application
  3. 3. Check the currently installed version by opening Framemaker and going to Help > About Adobe Framemaker
  4. 4. If running version 2020.8 or earlier, upgrade to version 2020.9 or later
  5. 5. If running version 2022.6 or earlier (2022.x versions), upgrade to version 2022.7 or later
  6. 6. Download and install the appropriate fixed version
  7. 7. After installation, verify the new version by checking Help > About Adobe Framemaker
  8. 8. Ensure the installed version is 2020.9 or later for the 2020 product line, or 2022.7 or later for the 2022 product line
Caveat Standard upgrade considerations apply - review Adobe's release notes for compatibility with existing documents and any configuration changes needed

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

Fix this in Framemaker 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-47122 — 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-47122 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