dbcve.org
FramemakerApplication · Adobe

CVE-2025-30296

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 an Integer Underflow (Wrap or Wraparound) 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

Adobe Framemaker contains an integer underflow vulnerability where arithmetic operations can wrap around to produce unexpectedly small values, leading to memory corruption. Successful exploitation allows arbitrary code execution in the context of the current user when a victim opens a specially crafted malicious file.

MitigationUpdate Adobe Framemaker to the latest patched version (contact Adobe for specific patch information). Avoid opening untrusted or unexpected files from unknown sources until the update 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
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. Check if Adobe Framemaker is installed
    On Windows, open Control Panel > Programs and Features and look for Adobe Framemaker, or search for framemaker.exe in Program Files. On macOS, check /Applications for Adobe Framemaker.
    Affected if Adobe Framemaker is present on the system
  2. Determine installed version number
    Open Adobe Framemaker and go to Help > About Adobe Framemaker to see the exact version, or check the Windows Registry key HKEY_LOCAL_MACHINE\SOFTWARE\Adobe\FrameMaker\Version for the Version value
    Affected if Unable to determine version - if Framemaker is installed but version cannot be verified, treat as potentially affected
  3. Compare version against affected ranges
    Check if the version starts with 2020.x where x is less than 8 (such as 2020.1, 2020.5, 2020.7), or 2022.x where x is less than 6 (such as 2022.1, 2022.4, 2022.5)
    Affected if Version matches pattern 2020.0 through 2020.7 or 2022.0 through 2022.5
  4. Confirm attack surface is accessible
    Verify that Framemaker can open document files - this is the default behavior and the vulnerability is triggered when opening a specially crafted file
    Affected if Framemaker can open files, which is the default configuration

System is affected if Adobe Framemaker is installed with a version in the range 2020.0 to 2020.7 or 2022.0 to 2022.5

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 (contact Adobe for specific patch information). Avoid opening untrusted or unexpected files from unknown sources until the update is applied.

Recommended fix High confidence

Adobe Framemaker 2022.6 or later (for both 2020.x and 2022.x product lines)

  1. 1. Verify current Adobe Framemaker version by opening the application and navigating to Help > About Adobe Framemaker
  2. 2. Close any running instances of Adobe Framemaker
  3. 3. Download Adobe Framemaker 2022.6 or later from the official Adobe website (get.adobe.com/framemaker) or through your organization's Adobe Admin Console
  4. 4. Run the installer with administrator privileges
  5. 5. Follow the on-screen installation prompts to complete the upgrade
  6. 6. After installation, verify the version by checking Help > About Adobe Framemaker to confirm the new version is installed
Caveat Standard upgrade considerations apply - backup custom configurations and templates before upgrading; test existing workflows with the new version before production deployment

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
  • Testing1.0 h
  • Review / QA1.0 h
5.0 hours of engineering $910
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,456.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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