dbcve.org
FramemakerApplication · Adobe

CVE-2025-30297

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 out-of-bounds write 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 versions 2020.8, 2022.6 and earlier contain an out-of-bounds write vulnerability that allows arbitrary code execution when a victim opens a specially crafted malicious file. The vulnerability exploits memory corruption to achieve code execution in the context of the current user.

MitigationApply vendor-provided patches for Adobe Framemaker when available. Until patches are released, avoid opening untrusted or unexpected files and restrict user permissions to limit impact of potential exploitation.

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. Identify if Adobe Framemaker is installed
    On Windows, open Control Panel > Programs and Features and look for 'Adobe Framemaker' in the list of installed software. Alternatively, check the Windows Registry under HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\ for an entry containing 'Adobe Framemaker'.
    Affected if Adobe Framemaker is present on the system.
  2. Determine the installed version of Adobe Framemaker
    In Windows Programs and Features, the version is shown in the 'Version' column next to Adobe Framemaker. If not visible there, launch Adobe Framemaker and go to Help > About Adobe Framemaker to display the exact version number.
    Affected if The installed version cannot be determined or the software is not listed.
  3. Compare the installed version against affected ranges
    Compare the identified version number to the affected ranges: versions 2020.x where x is less than 8 (such as 2020.0 through 2020.7), and versions 2022.x where x is less than 6 (such as 2022.0 through 2022.5). Versions 2020.8 and later, and 2022.6 and later, are NOT affected.
    Affected if The installed version falls within >= 2020, < 2020.8 OR >= 2022, < 2022.6.
  4. Assess user exposure to untrusted files
    Determine whether the system user role typically opens document files from external or untrusted sources. This vulnerability is triggerable only when a user opens a specially crafted malicious file. Check file handling behaviors and user workflows.
    Affected if Users routinely open .fm, .xml, or other document files from untrusted or unknown sources without prior validation.

A user is affected if Adobe Framemaker is installed with a version matching 2020.x < 2020.8 or 2022.x < 2022.6 AND the application is used to open files from untrusted or unexpected sources.

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 vendor-provided patches for Adobe Framemaker when available. Until patches are released, avoid opening untrusted or unexpected files and restrict user permissions to limit impact of potential exploitation.

Recommended fix High confidence

Adobe Framemaker 2020.8 or later, or Adobe Framemaker 2022.6 or later (whichever major version line you are on)

  1. 1. Verify current Adobe Framemaker version by opening the application and navigating to Help > About Adobe Framemaker
  2. 2. If running a version >= 2020 and < 2020.8, or >= 2022 and < 2022.6, download the patched version from the official Adobe website
  3. 3. Close all instances of Adobe Framemaker
  4. 4. Run the installer for the fixed version (2020.8 or 2022.6 and later)
  5. 5. Follow the on-screen installation prompts
  6. 6. After installation, verify the new version by checking Help > About Adobe Framemaker
Caveat Standard upgrade considerations apply - test existing documents for compatibility with the new version before deploying widely

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
  • Testing4.0 h
  • Review / QA2.0 h
10.0 hours of engineering $1,720
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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