dbcve.org
FramemakerApplication · Adobe

CVE-2025-47123

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. This memory corruption leads to arbitrary code execution in the context of the current user.

MitigationUsers should avoid opening untrusted or unexpected files and should update to the latest patched version of Adobe Framemaker when released. Organizations should deploy vendor patches promptly and consider application whitelisting to mitigate risks from malicious file handling.

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. Confirm Adobe Framemaker is installed
    Check for the presence of Adobe Framemaker installation directory under C:\Program Files\Adobe\ or C:\Program Files (x86)\Adobe\, or query the Windows Registry under HKLM\SOFTWARE\Adobe\Adobe FrameMaker for installed instances
    Affected if No Adobe Framemaker installation is found, then the system is not affected by this CVE
  2. Identify installed Framemaker version
    Open the installation directory and locate the executable (framemaker.exe or fminet.exe), right-click and view Properties, or query the Windows Registry key HKLM\SOFTWARE\Adobe\Adobe FrameMaker\[version] for the "Version" value
    Affected if Unable to determine the version number from the executable or registry, cannot confirm exposure to the CVE
  3. Compare version against affected ranges
    If version is 2020.x, check if it is less than 2020.9. If version is 2022.x, check if it is 2022.6 or earlier (less than 2022.7). Versions outside 2020 and 2022 lines may have different version schemes
    Affected if The installed version falls within < 2020.9 or >= 2022 and < 2022.7, indicating the system is vulnerable to this CVE
  4. Verify file handling exposure
    Determine if the system routinely opens .fm, .mif, or other Framemaker document types from untrusted sources, or if application execution policies permit running Framemaker with arbitrary file inputs
    Affected if Users have the ability to open received or downloaded Framemaker documents directly, creating the conditions necessary to trigger the heap overflow

A user is affected if Adobe Framemaker is installed with a version below 2020.9 or between 2022.0 and 2022.6 inclusive, and the application can be used 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

Users should avoid opening untrusted or unexpected files and should update to the latest patched version of Adobe Framemaker when released. Organizations should deploy vendor patches promptly and consider application whitelisting to mitigate risks from malicious file handling.

Recommended fix High confidence

Adobe Framemaker 2020.9 or later for the 2020.x line; Adobe Framemaker 2022.7 or later for the 2022.x line

  1. 1. Open Adobe Framemaker and navigate to Help > About Adobe Framemaker to verify the current installed version.
  2. 2. If version is 2020.8 or earlier, download Adobe Framemaker 2020.9 or later from the official Adobe website (helpx.adobe.com).
  3. 3. If version is 2022.0 through 2022.6, download Adobe Framemaker 2022.7 or later from the official Adobe website (helpx.adobe.com).
  4. 4. Close all instances of Framemaker before running the installer.
  5. 5. Run the downloaded installer and follow the on-screen prompts to complete the update.
  6. 6. After installation, verify the new version 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
  • Consultation2.0 h
  • Implementation3.0 h
  • Testing2.0 h
  • Review / QA1.0 h
8.0 hours of engineering $1,420
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,272.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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