dbcve.org
FramemakerApplication · Adobe

CVE-2025-30302

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 an out-of-bounds read vulnerability that could lead to disclosure of sensitive memory. An attacker could leverage this vulnerability to bypass mitigations such as ASLR. 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 read vulnerability that allows disclosure of sensitive memory contents when processing malicious files. This information disclosure can be leveraged by attackers to bypass ASLR (Address Space Layout Randomization) mitigations, potentially facilitating further exploitation. Successful exploitation requires user interaction, specifically that the victim opens a crafted malicious file.

MitigationUpdate Adobe Framemaker to the latest patched version provided by Adobe. Additionally, educate users about the risks of opening files from untrusted sources and consider deploying additional email/gateway scanning to detect malicious file 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, < 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
High
Integrity
None
Availability
None

CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:N/A:N

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
    Windows: Check Control Panel > Programs and Features for Adobe Framemaker, or look in C:\Program Files\Adobe\Adobe FrameMaker\; macOS: Check /Applications for Adobe Framemaker.app
    Affected if Adobe Framemaker is present on the system
  2. Identify installed version number
    Windows: Locate framemaker.exe in the installation folder, right-click > Properties > Details tab > Product Version; macOS: Right-click Adobe Framemaker.app > Get Info > Version
    Affected if Version cannot be determined or falls within affected ranges
  3. Compare version against affected ranges
    Check if version is 2020.x where x < 8 (2020.0 through 2020.7), OR 2022.x where x < 6 (2022.0 through 2022.5)
    Affected if Version matches 2020.x < 2020.8 OR 2022.x < 2022.6
  4. Assess file processing exposure
    Determine if users in the environment open Adobe Framemaker document files (.fm, .book, .mif) from external or untrusted sources, or receive these files via email or downloads
    Affected if Users process untrusted Framemaker files as part of normal workflow

User is affected if Adobe Framemaker version 2020.x < 2020.8 or 2022.x < 2022.6 is installed AND users can be persuaded to open a crafted malicious file.

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 the latest patched version provided by Adobe. Additionally, educate users about the risks of opening files from untrusted sources and consider deploying additional email/gateway scanning to detect malicious file attachments.

Recommended fix High confidence

Adobe Framemaker 2022.6 (recommended, as 2022.x is the newer release line)

  1. 1. Close Adobe Framemaker if it is currently running.
  2. 2. Backup any important documents or workspace configurations as a precautionary measure.
  3. 3. For Framemaker 2020.x users: Upgrade to version 2020.8 or later.
  4. 4. For Framemaker 2022.x users: Upgrade to version 2022.6 or later.
  5. 5. Download the appropriate update from the Adobe HelpX portal at helpx.adobe.com or use the Adobe Creative Cloud desktop application to apply the update.
  6. 6. After installation, verify the version by opening Framemaker and navigating to Help > About Adobe Framemaker to confirm the installed version.
  7. 7. Warn users against opening untrusted or unexpected MIF/FrameMaker documents from unknown sources, as exploitation requires user interaction.
Caveat Standard upgrade considerations apply - verify compatibility of custom scripts, templates, and third-party plugins with the new version before deploying organization-wide

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
  • Testing2.0 h
  • Review / QA1.0 h
7.0 hours of engineering $1,240
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,984.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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