dbcve.org
FramemakerApplication · Adobe

CVE-2025-54233

MEDIUM · 5.5 CVSS v3.1 Published 2025-08-12
Fix available
A fix is available. Upgrade to 2020.9 / 2022.7 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. 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 out-of-bounds read vulnerability when parsing certain files, allowing memory disclosure beyond allocated buffer boundaries. Successful exploitation requires a victim to open a specially crafted malicious file, leading to potential exposure of sensitive memory contents.

MitigationUpdate Adobe Framemaker to the latest version beyond 2020.8 and 2022.6 when available, and exercise caution by not opening files from untrusted sources.

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.9>= 2022, < 2022.7

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. Confirm Adobe Framemaker is installed
    Open Windows Control Panel > Programs and Features, or check C:\Program Files\Adobe\Adobe Framemaker for the executable
    Affected if Adobe Framemaker appears in installed programs or the executable folder exists
  2. Locate the Framemaker executable version
    Right-click the Framemaker executable (framemaker.exe) in the installation folder, select Properties, and view the Details tab for the Product Version
    Affected if The product version cannot be determined or the file does not exist
  3. Compare installed version against affected ranges
    If version is 2020.x, ensure it is 2020.9 or later; if version is 2022.x, ensure it is 2022.7 or later. Versions below these thresholds are vulnerable
    Affected if Installed version is earlier than 2020.9, or is 2022.0 through 2022.6
  4. Verify the attack vector requires user interaction
    This vulnerability is triggered only when Framemaker opens a specially crafted malicious file. Check whether users in your environment open files from untrusted or unknown sources
    Affected if Users routinely open document files from untrusted or unknown sources in Framemaker

You are affected if Adobe Framemaker is installed with a version earlier than 2020.9 (2020.x line) or between 2022.0 and 2022.6 (2022.x line), and users may open files from untrusted 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.9 / 2022.7 or later
Fixed in 2020.92022.7
Interim mitigation

Update Adobe Framemaker to the latest version beyond 2020.8 and 2022.6 when available, and exercise caution by not opening files from untrusted sources.

Recommended fix High confidence

Adobe Framemaker 2020.9 or later; Adobe Framemaker 2022.7 or later (depending on your release track)

  1. 1. Identify the currently installed Adobe Framemaker version via Help > About Adobe Framemaker
  2. 2. For Framemaker 2020.x users: Upgrade to version 2020.9 or later
  3. 3. For Framemaker 2022.x users: Upgrade to version 2022.7 or later
  4. 4. Download the updated version from the official Adobe website or use Adobe Creative Cloud desktop application to update
  5. 5. Restart the application after installation
  6. 6. Verify the installed version reflects the patched release
Caveat Minor - As a major version-to-version upgrade, test critical documents and custom workflows for compatibility with the new release

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