dbcve.org
FramemakerApplication · Adobe

CVE-2025-47132

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 can be triggered when a user opens a malicious file, leading to arbitrary code execution in the context of the current user.

MitigationUpdate Adobe Framemaker to a patched version. Until patched, instruct users to avoid opening files from untrusted 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. Verify Adobe Framemaker is installed
    On Windows, check the registry key HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\ for an entry containing 'Adobe Framemaker', or look for the executable at C:\Program Files\Adobe\Adobe Framemaker\. On macOS, check /Applications for Adobe Framemaker.app.
    Affected if Adobe Framemaker is not present on the system, the system is not affected.
  2. Determine the installed version number
    On Windows, right-click the Framemaker executable (framemaker.exe) in the install directory, select Properties, and view the File version on the Details tab. On macOS, right-click Adobe Framemaker.app, select Get Info, and view the Version field.
    Affected if Unable to determine the version means further verification is needed.
  3. Compare version against affected ranges
    The affected versions are: 2020.8 and earlier (any version < 2020.9), and versions 2022.0 through 2022.6 (any version >= 2022 but < 2022.7). Compare your installed version number to these ranges.
    Affected if Installed version falls within < 2020.9 or >= 2022 and < 2022.7, the system is potentially affected.
  4. Identify if Framemaker handles document files
    Check file associations or default program settings to see if .fm, .mif, or other Framemaker file types are associated with Adobe Framemaker, or review recent file open activity in the Framemaker application log.
    Affected if Users actively open .fm, .mif or other Framemaker document files with this application, the exploit can be triggered.

A system is affected if Adobe Framemaker is installed with a version number less than 2020.9, or between 2022.0 and 2022.6 inclusive, and users open Framemaker document 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. Until patched, instruct users to avoid opening files from untrusted sources.

Recommended fix High confidence

Adobe Framemaker 2020.9 or later (2020 branch); Adobe Framemaker 2022.7 or later (2022 branch)

  1. Check current Adobe Framemaker version by opening the application and navigating to Help > About Adobe Framemaker
  2. Identify which version branch your installation belongs to (2020.x or 2022.x)
  3. For Framemaker 2020.x users: Upgrade to version 2020.9 or later
  4. For Framemaker 2022.x users: Upgrade to version 2022.7 or later
  5. Download the updated version from the official Adobe website or your organization's software distribution point
  6. Verify installation of the patched version after upgrading
  7. Ensure users are warned not to open untrusted MIF/DTD/XML files until patches are applied

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

Fix this in Framemaker Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing4.0 h
  • Review / QA2.0 h
10.0 hours of engineering $1,720
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,752.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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