dbcve.org
FramemakerApplication · Adobe

CVE-2025-30303

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 contains an out-of-bounds read vulnerability allowing memory disclosure beyond buffer boundaries. An attacker can craft a malicious file that, when opened by a victim, leaks sensitive memory contents which can be leveraged to defeat ASLR. This is a classic memory corruption vulnerability exploitable through file parsing.

MitigationRestrict opening of untrusted .fm or related document files until Adobe releases an official patch. Deploy endpoint protection and email/content filtering to detect malicious file attachments. Consider adding Adobe Framemaker to application control whitelisting to prevent execution of unapproved instances.

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. Check if Adobe Framemaker is installed
    On Windows: Look for Adobe Framemaker in Programs and Features, or check Registry key HKLM\SOFTWARE\Adobe\Adobe Framemaker. On macOS: Check /Applications folder for Adobe Framemaker.app
    Affected if Adobe Framemaker is not installed means not affected
  2. Determine the installed version number
    On Windows: Right-click the installed Framemaker executable (typically in C:\Program Files\Adobe\Adobe Framemaker) and view Properties > Details for Product Version. Alternatively, run: reg query "HKLM\SOFTWARE\Adobe\Adobe Framemaker" /v Version
    Affected if Version cannot be determined means you cannot confirm patch status
  3. Compare version against affected ranges
    Identify if your version falls into: 2020.0 through 2020.7 (less than 2020.8), OR 2022.0 through 2022.5 (less than 2022.6). Versions 2020.8 and later, and 2022.6 and later are not affected
    Affected if Installed version is 2020.x where x < 8, OR 2022.x where x < 6, means vulnerable to this CVE
  4. Verify file parsing is accessible
    Confirm the application can open .fm document files. Check if the application is configured to handle .fm file associations or if users can import/open .fm files directly
    Affected if Users can open or import .fm files with a vulnerable version means the memory disclosure can be triggered

A user is affected if Adobe Framemaker version is 2020.0-2020.7 or 2022.0-2022.5 AND the application can open or process .fm document 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

Restrict opening of untrusted .fm or related document files until Adobe releases an official patch. Deploy endpoint protection and email/content filtering to detect malicious file attachments. Consider adding Adobe Framemaker to application control whitelisting to prevent execution of unapproved instances.

Recommended fix High confidence

Adobe Framemaker 2020.8 (for 2020.x line) or Framemaker 2022.6 (for 2022.x line)

  1. 1. Close Adobe Framemaker if it is currently running
  2. 2. Back up any important documents and settings
  3. 3. Identify the currently installed Framemaker version via Help > About Adobe Framemaker
  4. 4. For Framemaker 2020.x users: Navigate to helpx.adobe.com and download Framemaker 2020.8 or later
  5. 5. For Framemaker 2022.x users: Navigate to helpx.adobe.com and download Framemaker 2022.6 or later
  6. 6. Run the installer with administrator privileges
  7. 7. Complete the installation wizard and restart the system
  8. 8. After installation, verify the new version via Help > About Adobe Framemaker
Caveat Major version upgrades may introduce UI changes or compatibility issues with existing templates/scripts; test in non-production environment first

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

Fix this in Framemaker Scoped from the published advisory
  • Consultation3.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
17.0 hours of engineering $3,000
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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