dbcve.org
FramemakerApplication · Adobe

CVE-2025-47119

MEDIUM · 5.5 CVSS v3.1 Published 2025-07-08
Fix available
A fix is available. Upgrade to 2020.9 / 2022.7 or later.
See remediation →
58/100
Remediation priority · Elevated
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 NULL Pointer Dereference vulnerability that could lead to application denial-of-service. An attacker could exploit this vulnerability to crash the application, causing a disruption in service. 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 a NULL Pointer Dereference vulnerability that can be triggered when a user opens a malicious file, causing the application to crash and result in denial-of-service.

MitigationApply the vendor-provided security patch for Adobe Framemaker when available, and educate users to avoid opening untrusted 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
None
Integrity
None
Availability
High

CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:N/I:N/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 directory
    Check the default installation path on Windows: C:\Program Files\Adobe\ for folders named 'Adobe FrameMaker2020' or 'Adobe FrameMaker2022'. If installed to a custom directory, search for 'framemaker.exe' using File Explorer search.
    Affected if The Adobe Framemaker installation directory exists on the system.
  2. Check installed Framemaker version via registry
    Open Windows Registry Editor (regedit.exe) and navigate to HKLM\SOFTWARE\Adobe\Adobe FrameMaker\Version. Note the string value shown in the right pane.
    Affected if The registry key exists and contains a version number.
  3. Compare version to vulnerable ranges
    If version is 2020.x, ensure it is 2020.9 or later. If version is 2022.x, ensure it is 2022.7 or later. Versions 2020.8 and earlier, or 2022.0 through 2022.6, are vulnerable.
    Affected if The installed version is 2020.8 or earlier, OR between 2022.0 and 2022.6 inclusive.
  4. Verify file association or recent document access
    Check if .fm or other FrameMaker file types are associated with the application, or review recently opened files in the application to confirm user interaction with untrusted files is possible.
    Affected if Users can open .fm files with the vulnerable application version.

A system is affected if Adobe Framemaker version 2020.8 or earlier, or version 2022.0 through 2022.6, is installed and users can open document files with it.

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

Apply the vendor-provided security patch for Adobe Framemaker when available, and educate users to avoid opening untrusted files from unknown sources.

Recommended fix Moderate confidence

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

  1. 1. Ensure you have a backup of all important Framemaker documents and settings.
  2. 2. Close Adobe Framemaker completely if it is currently running.
  3. 3. Uninstall the current version of Adobe Framemaker from your system.
  4. 4. Download Adobe Framemaker 2020.9 or later (for the 2020.x line) OR version 2022.7 or later (for the 2022.x line) from the official Adobe website or Adobe Creative Cloud desktop application.
  5. 5. Run the installer for the chosen fixed version and follow the on-screen prompts to complete the installation.
  6. 6. After installation, verify the version by opening Framemaker and checking Help > About Adobe Framemaker to confirm you are on a patched version (2020.9+, 2022.7+, or later).
  7. 7. Test that normal document operations work correctly after the upgrade.

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
  • Testing2.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,060
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,696.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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