dbcve.org
FramemakerApplication · Adobe

CVE-2025-30295

HIGH · 7.8 CVSS v3.1 Published 2025-04-08
Fix available
A fix is available. Upgrade to 2020.8 / 2022.6 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 a Heap-based Buffer Overflow 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 · moderate confidence

Heap-based buffer overflow vulnerability in Adobe Framemaker (versions 2020.8, 2022.6 and earlier) allows arbitrary code execution when a user opens a malicious file. The vulnerability operates in the context of the current user session, making it exploitable via socially engineered documents that trigger the overflow during file parsing.

MitigationApply the vendor-provided security patch for Adobe Framemaker to address this vulnerability. Until patched, instruct users to avoid opening files from untrusted sources, as exploitation requires user interaction (opening a malicious document).

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
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 installation
    Use system inventory tools or check common installation directories (typically C:\Program Files\Adobe\Adobe FrameMaker or C:\Program Files (x86)\Adobe\Adobe FrameMaker on Windows; /Applications/Adobe FrameMaker on macOS) to confirm the product is installed.
    Affected if Adobe Framemaker is present on the system
  2. Determine installed version number
    Locate the installed version through the application's properties (right-click executable > Properties > Details), the Windows Registry (HKLM\SOFTWARE\Adobe\FrameMaker\Version), or the system's installed programs list (Add/Remove Programs or Apps & Features).
    Affected if Version cannot be determined but product is installed
  3. Compare against affected version ranges
    Review the identified version against the affected ranges: versions >= 2020 and < 2020.8, or versions >= 2022 and < 2022.6. Note that versions 2020.8 through 2021.x are NOT affected, and versions 2022.6 and later are NOT affected.
    Affected if Installed version falls within >= 2020, < 2020.8 OR >= 2022, < 2022.6

A user is affected if Adobe Framemaker is installed with a version that falls within the 2020.x (before 2020.8) or 2022.x (before 2022.6) ranges, as these versions contain the vulnerable code that can be triggered by opening a 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

Apply the vendor-provided security patch for Adobe Framemaker to address this vulnerability. Until patched, instruct users to avoid opening files from untrusted sources, as exploitation requires user interaction (opening a malicious document).

Recommended fix High confidence

Adobe Framemaker 2020.8 or later; Adobe Framemaker 2022.6 or later

  1. 1. Verify current Adobe Framemaker version by opening the application and navigating to Help > About Adobe Framemaker
  2. 2. For Framemaker 2020 users: Upgrade to version 2020.8 or later (the next release after 2020.7)
  3. 3. For Framemaker 2022 users: Upgrade to version 2022.6 or later (the next release after 2022.5)
  4. 4. Download the updated version from the official Adobe website or use Adobe's Creative Cloud desktop application to update
  5. 5. After installation, confirm the version by checking Help > About Adobe Framemaker shows 2020.8 or later, or 2022.6 or later
  6. 6. Exercise caution with unsolicited files - this vulnerability requires user interaction to open a malicious file
Caveat Users should test critical workflows after upgrading as minor interface or compatibility changes may occur between major versions

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

Fix this in Framemaker Scoped from the published advisory
  • Consultation3.0 h
  • Implementation2.0 h
  • Testing4.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,920
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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