dbcve.org
FramemakerApplication · Adobe

CVE-2025-47133

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 victim opens a malicious file, running in the context of the current user's privileges.

MitigationDo not open untrusted or unexpected Framemaker files; update to patched versions when released; deploy file screening at email gateways to block suspicious attachments.

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
    Check for Framemaker installation via Windows Registry key at HKEY_LOCAL_MACHINE\SOFTWARE\Adobe\Adobe FrameMaker or HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\Adobe\Adobe FrameMaker, or look for Framemaker.exe in common install paths such as C:\Program Files\Adobe\Adobe FrameMaker 2020 or C:\Program Files\Adobe\Adobe FrameMaker 2022
    Affected if Adobe Framemaker is present on the system
  2. Determine installed Framemaker version
    Open Windows Registry and read the Version value from the Adobe FrameMaker registry key identified in step 1, or right-click Framemaker.exe in the installation directory and view Properties > Details for the Product Version
    Affected if The version cannot be determined or the software is present but version info is missing
  3. Compare version against affected 2020.x range
    If the installed version starts with 2020 (e.g., 2020.0, 2020.1, 2020.2, ... 2020.8), verify whether it is less than 2020.9. Extract the minor version number after 2020. and check if it is 8 or lower
    Affected if Version is 2020.8 or any earlier 2020.x release (2020.0 through 2020.8)
  4. Compare version against affected 2022.x range
    If the installed version starts with 2022 (e.g., 2022.0, 2022.1, 2022.2, ... 2022.6), verify whether it is less than 2022.7. Extract the minor version number after 2022. and check if it is 6 or lower
    Affected if Version is 2022.6 or any earlier 2022.x release (2022.0 through 2022.6)

A user is affected if Adobe Framemaker is installed and the version matches 2020.x prior to 2020.9 or 2022.x prior to 2022.7, and the user opens untrusted malicious 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

Do not open untrusted or unexpected Framemaker files; update to patched versions when released; deploy file screening at email gateways to block suspicious attachments.

Recommended fix High confidence

Adobe Framemaker 2020.9 or later, or 2022.7 or later

  1. 1. Verify current Adobe Framemaker installation version via Help > About Adobe Framemaker
  2. 2. For Framemaker 2020.x users: Upgrade to version 2020.9 or later
  3. 3. For Framemaker 2022.x users: Upgrade to version 2022.7 or later
  4. 4. Download the updated version from the official Adobe website or through your Adobe admin console
  5. 5. Restart the application after installation
  6. 6. Apply any additional Adobe security patches as they become available
Caveat Standard upgrade; ensure system meets minimum requirements for the new version

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

Fix this in Framemaker Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing4.0 h
  • Review / QA2.0 h
15.0 hours of engineering $2,640
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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