dbcve.org
FramemakerApplication · Adobe

CVE-2025-47125

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 · moderate 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 specially crafted malicious file, potentially allowing arbitrary code execution in the context of the current user.

MitigationUpdate Adobe Framemaker to a patched version beyond 2020.8 and 2022.6; avoid opening untrusted or unexpected .fm files from unknown sources 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
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 installed Adobe Framemaker version
    Open Adobe Framemaker, then go to Help > About Adobe Framemaker to display the installed version number. Alternatively, check the Windows Registry under HKLM\SOFTWARE\Adobe\Framemaker\Version or on macOS under /Applications/Adobe Framemaker/Contents/Info.plist for the CFBundleShortVersionString value.
    Affected if The displayed version is 2020.8 or earlier, OR any version from 2022.0 through 2022.6 inclusive.
  2. Verify exact version against vulnerable ranges
    Compare your identified version number to the affected ranges: versions below 2020.9 (such as 2020.8, 2020.7, etc.) are vulnerable, and versions 2022.0 through 2022.6 are vulnerable. Versions 2020.9 and later, and 2022.7 and later, are not affected.
    Affected if The installed version falls within < 2020.9 or >= 2022.0 but < 2022.7.
  3. Identify .fm file handling context
    Determine whether Adobe Framemaker is configured to open .fm files on your system. Check file associations in your OS or within Framemaker (Edit > Preferences > File Associations) to see if .fm files are registered.
    Affected if Adobe Framemaker is set as the default handler for .fm files and the version is vulnerable per step 2.

You are affected if Adobe Framemaker version is 2020.8 or earlier, or any version from 2022.0 to 2022.6, and you open .fm files with the application.

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 beyond 2020.8 and 2022.6; avoid opening untrusted or unexpected .fm files from unknown sources until the patch is applied.

Recommended fix High confidence

Adobe Framemaker 2020.9 or later, or Adobe Framemaker 2022.7 or later

  1. 1. Close any running instances of Adobe Framemaker
  2. 2. Backup your current Framemaker documents and settings
  3. 3. Uninstall the current version of Adobe Framemaker
  4. 4. Download Adobe Framemaker 2020.9 or later from the official Adobe website, or download version 2022.7 or later for the 2022 branch
  5. 5. Install the updated version by running the downloaded installer
  6. 6. Restart your computer after installation completes
  7. 7. Open Adobe Framemaker and verify the version by going to Help > About Adobe Framemaker
  8. 8. Do not open any untrusted or unsolicited files received via email or from unknown sources

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

Fix this in Framemaker Scoped from the published advisory
  • Consultation2.0 h
  • Implementation1.0 h
  • Testing3.0 h
  • Review / QA2.0 h
8.0 hours of engineering $1,390
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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