dbcve.org
FramemakerApplication · Adobe

CVE-2025-47124

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 an out-of-bounds write 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 an out-of-bounds write vulnerability that allows arbitrary code execution when a user opens a malicious crafted file. The vulnerability executes in the context of the current user's privileges.

MitigationUpdate Adobe Framemaker to the latest patched version. Until then, warn users not to open untrusted or unexpected Framemaker 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
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
    Check for Framemaker.exe in typical installation paths such as C:\Program Files\Adobe\Adobe FrameMaker 2022\ or C:\Program Files\Adobe\Adobe FrameMaker 2020\, or query the Windows Registry under HKLM\SOFTWARE\Adobe\Adobe Framemaker for the InstallPath value
    Affected if Framemaker is installed on the system
  2. Determine installed Framemaker version
    Right-click Framemaker.exe, select Properties, and check the File Version field, or run the command: wmic product where "name like 'Adobe FrameMaker%'" get version
    Affected if The version returned is 2020.8 or earlier, or falls between 2022.0 and 2022.6 inclusive
  3. Confirm version is within affected range
    Compare your installed version number against the vulnerable ranges: any version below 2020.9, or any version from 2022.0 through 2022.6
    Affected if The installed version matches either < 2020.9 or >= 2022.0 but < 2022.7
  4. Identify file association risk
    Check if .fm or other Framemaker file types are associated with Framemaker by reviewing file associations in Windows Settings > Apps > Default Apps, or by examining HKCR\.fm\OpenWithProgids in the registry
    Affected if Framemaker is set as the default handler for .fm files, allowing automatic opening of malicious documents

If Adobe Framemaker is installed and its version falls below 2020.9 or between 2022.0 and 2022.6, the system is vulnerable when users open untrusted Framemaker documents.

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 the latest patched version. Until then, warn users not to open untrusted or unexpected Framemaker files from unknown sources.

Recommended fix High confidence

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

  1. 1. Close all instances of Adobe Framemaker
  2. 2. Back up any important documents and settings
  3. 3. Navigate to the Adobe Framemaker download page at helpx.adobe.com
  4. 4. Download the latest version: 2022.7 or later for the 2022.x line, or 2020.9 or later for the 2020.x line
  5. 5. Run the installer and follow the on-screen prompts
  6. 6. Verify the installed version matches the fixed release by checking Help > About Adobe Framemaker

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

Fix this in Framemaker Scoped from the published advisory
  • Consultation1.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,040
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,664.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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