dbcve.org
FramemakerApplication · Adobe

CVE-2025-30299

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 victim opens a malicious file, running in the context of the current user.

MitigationDo not open untrusted or unexpected files in Adobe Framemaker. Update to a patched version once released by Adobe.

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 is installed
    On Windows, open Registry Editor and navigate to HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall or HKEY_CURRENT_USER\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall. Look for a key with DisplayName containing 'Adobe Framemaker'. Alternatively, check C:\Program Files\Adobe\ or C:\Program Files (x86)\Adobe\ for a Framemaker folder.
    Affected if Adobe Framemaker is found installed on the system
  2. Locate the Framemaker executable
    In the identified Adobe Framemaker installation folder, locate FrameMaker.exe. On 64-bit systems it may be in a subfolder like 'Adobe Framemaker 2020\Core' or similar.
    Affected if FrameMaker.exe exists in the installation directory
  3. Determine the installed version number
    Right-click FrameMaker.exe, select Properties, then go to the Details tab. Note the File Version or Product Version. Alternatively, run 'wmic product get name,version' or check the same registry key from step 1 for the Version value.
    Affected if The displayed version is a numeric value like 2020.x or 2022.x
  4. Compare version against affected ranges
    If version starts with 2020: ensure it is 2020.8 or later (e.g., 2020.8.0.0). If version starts with 2022: ensure it is 2022.6 or later (e.g., 2022.6.0.0). Versions 2020.0 through 2020.7 and 2022.0 through 2022.5 are affected.
    Affected if The installed version is 2020.0 through 2020.7 OR 2022.0 through 2022.5 (i.e., it is before 2020.8 or before 2022.6)
  5. Confirm the vulnerability trigger condition
    This vulnerability requires a user to open a maliciously crafted file in Adobe Framemaker. Check whether users in your environment commonly open MIF, XML, or other document files from untrusted sources.
    Affected if Users routinely open files from untrusted or unknown sources in Framemaker

A user is affected if Adobe Framemaker is installed with version 2020.0-2020.7 or 2022.0-2022.5 AND the user opens malicious files.

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

Do not open untrusted or unexpected files in Adobe Framemaker. Update to a patched version once released by Adobe.

Recommended fix High confidence

Framemaker 2020.8 or later for 2020.x releases; Framemaker 2022.6 or later for 2022.x releases

  1. Close Adobe Framemaker if it is currently running
  2. Back up any important Framemaker documents as a precaution
  3. Open Adobe Creative Cloud Desktop app or navigate to helpx.adobe.com/framemaker
  4. Check for available updates or download Framemaker version 2020.8 or later (for the 2020 release line)
  5. Alternatively, download Framemaker version 2022.6 or later (for the 2022 release line)
  6. Run the installer and follow the on-screen prompts to complete the upgrade
  7. Launch Framemaker and verify the version by selecting Help > About Adobe FrameMaker
Caveat Standard patch update with minimal breaking changes; verify compatibility with custom plugins or scripts

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