CVE-2025-30304
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 · uneditedAdobe 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 · high confidenceAdobe Framemaker versions 2020.8, 2022.6 and earlier contain an out-of-bounds write vulnerability that allows arbitrary code execution when a user opens a malicious file. The vulnerability operates in the context of the current user's privileges.
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>= 2020, < 2020.8>= 2022, < 2022.6CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Confirm Adobe Framemaker is installedOpen Windows Control Panel > Programs and Features, or check C:\Program Files\Adobe\Adobe FrameMaker for the executableAffected if Adobe Framemaker is present on the system
-
Identify the installed Framemaker versionRight-click on the Framemaker executable (framemaker.exe) in Program Files, select Properties, and view the File Version details. Alternatively, launch Framemaker and go to Help > About Adobe Framemaker to see the exact version numberAffected if The displayed version falls within 2020.0 to 2020.7, or 2022.0 to 2022.5
-
Verify the vulnerability trigger conditionThis vulnerability is triggered when a user opens a specially crafted malicious file. Confirm that Framemaker is configured to open document files (such as .fm, .mif, or other supported formats)Affected if Framemaker can open document files and the identified version is in the affected range
You are affected if Adobe Framemaker is installed and the identified version is 2020.0 through 2020.7 or 2022.0 through 2022.5
Generated from the published advisory. Verify against your own configuration.
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 · scoped2020.82022.6
Upgrade Adobe Framemaker to a patched version. Avoid opening untrusted or unexpected files from unknown sources until the update is applied.
Framemaker 2020.8 or later; Framemaker 2022.6 or later
- 1. Identify the currently installed Adobe Framemaker version from the application (Help > About Adobe Framemaker)
- 2. For Framemaker 2020 (versions 2020.0 through 2020.7): Upgrade to version 2020.8 or later
- 3. For Framemaker 2022 (versions 2022.0 through 2022.5): Upgrade to version 2022.6 or later
- 4. Download the appropriate updated version from the official Adobe website or use the Adobe Creative Cloud desktop application to update
- 5. Verify the installation completed successfully and confirm the new version number
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation4.0 h
- Testing6.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,808.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-30304 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2025-30304 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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