dbcve.org
FramemakerApplication · Adobe

CVE-2025-30301

MEDIUM · 5.5 CVSS v3.1 Published 2025-04-08
Fix available
A fix is available. Upgrade to 2020.8 / 2022.6 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 result in an application denial-of-service. An attacker could exploit this vulnerability to crash the application, leading to a denial-of-service condition. 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. The vulnerability causes the application to crash, resulting in denial-of-service conditions.

MitigationUpdate Adobe Framemaker to a version newer than 2020.8 and 2022.6 when patches become available. Avoid opening untrusted or unexpected files until the patch is applied.

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, < 2020.8>= 2022, < 2022.6

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. Confirm Adobe Framemaker is installed
    Check for Framemaker installation on the system - look for Adobe Framemaker in installed programs (Windows) or application folder (Mac/Linux)
    Affected if Adobe Framemaker is not found on the system, this CVE does not apply
  2. Identify installed Framemaker version
    On Windows: Open Registry Editor and navigate to HKEY_LOCAL_MACHINE\SOFTWARE\Adobe\FrameMaker\Version (or HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\Adobe\FrameMaker\Version). On Mac: Check /Applications/Adobe FrameMaker 2020 or 2022/FrameMaker.app/Contents/Info.plist for CFBundleShortVersionString
    Affected if Unable to determine the installed version, manual verification required
  3. Compare version against affected ranges
    If version begins with 2020.x, check if it is less than 2020.8. If version begins with 2022.x, check if it is less than 2022.6
    Affected if Installed version is 2020.x where x < 8, OR installed version is 2022.x where x < 6, OR version is earlier than 2020 (e.g., 2019, 2017)
  4. Understand exploitation vector
    This vulnerability is triggered when a user opens a specially crafted malicious file. The NULL pointer dereference causes the application to crash
    Affected if The affected version is running and the user opens untrusted files - this confirms the attack surface exists

User is affected if Adobe Framemaker version 2020 through 2020.7 or 2022 through 2022.5 is installed and running on the system.

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.8 / 2022.6 or later
Fixed in 2020.82022.6
Interim mitigation

Update Adobe Framemaker to a version newer than 2020.8 and 2022.6 when patches become available. Avoid opening untrusted or unexpected files until the patch is applied.

Recommended fix High confidence

Framemaker 2020.8 or later; Framemaker 2022.6 or later

  1. 1. Verify the current Adobe Framemaker version by opening the application and navigating to Help > About Adobe Framemaker
  2. 2. For Framemaker 2020.x users: Upgrade to version 2020.8 or later (2020.8 contains the security fix)
  3. 3. For Framemaker 2022.x users: Upgrade to version 2022.6 or later (2022.6 contains the security fix)
  4. 4. Download the updated version from the official Adobe website or use the Creative Cloud desktop application to update
  5. 5. After installation, verify the version shows the patched release number
  6. 6. Apply standard least-privilege practices when opening files from untrusted sources
Caveat Standard upgrade considerations apply - review Adobe's release notes for any feature changes between versions

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-30301 — 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-30301 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