dbcve.org
FramemakerApplication · Adobe

CVE-2024-53959

HIGH · 7.8 CVSS v3.1 Published 2024-12-10
Fix available
A fix is available. Upgrade to 2020.7 / 2022.5 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.7, 2022.5 and earlier are affected by a Stack-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 · high confidence

Adobe Framemaker versions 2020.7, 2022.5 and earlier contain a stack-based buffer overflow vulnerability. An attacker can exploit this by crafting a malicious file that, when opened by a victim, triggers the overflow and executes arbitrary code in the context of the current user.

MitigationUpdate Adobe Framemaker to the latest patched version. Avoid opening files from untrusted or unknown 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.7>= 2022, < 2022.5

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. Check installed Adobe Framemaker version via Windows Settings
    Open Windows Settings > Apps > Installed apps (or Programs and Features). Search for 'Adobe Framemaker' and note the version number displayed.
    Affected if The version shown is 2020.x before 2020.7, or 2022.x before 2022.5 (including 2022.0 through 2022.4).
  2. Check Adobe Framemaker version from the application
    Launch Adobe Framemaker. Go to Help menu > About Adobe Framemaker. The version dialog will display the exact version number.
    Affected if The version shown is 2020.x before 2020.7, or 2022.x before 2022.5.
  3. Check Adobe Framemaker version via Windows Registry
    Open Registry Editor (regedit). Navigate to HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\{Adobe Framemaker product ID} or HKEY_CURRENT_USER\SOFTWARE\Adobe\Framemaker\ProductVersion. Check the DisplayVersion value.
    Affected if The DisplayVersion or ProductVersion value is less than 2020.7 for 2020.x releases, or less than 2022.5 for 2022.x releases.
  4. Verify Framemaker component versions via command line
    Open Command Prompt or PowerShell and run: wmic product where "name like 'Adobe Framemaker'" get name,version. Alternatively, check in PowerShell: Get-ItemProperty 'HKLM:\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\*' | Where-Object {$_.DisplayName -like '*Framemaker*'} | Select-Object DisplayName, DisplayVersion.
    Affected if The reported version is 2020.0 through 2020.6, or 2022.0 through 2022.4.

If Adobe Framemaker is installed and the version is 2020.x before 2020.7, or 2022.x before 2022.5, the environment is affected by this stack-based buffer overflow vulnerability.

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.7 / 2022.5 or later
Fixed in 2020.72022.5
Interim mitigation

Update Adobe Framemaker to the latest patched version. Avoid opening files from untrusted or unknown sources.

Recommended fix High confidence

Adobe Framemaker 2022.6 or later (or latest available release)

  1. 1. Verify current Adobe Framemaker version by opening the application and navigating to Help > About Adobe Framemaker
  2. 2. If version is less than 2020.7, upgrade to Framemaker 2020.7 or later
  3. 3. If version is 2022.x and less than 2022.5, upgrade to Framemaker 2022.6 or later
  4. 4. Download the appropriate version from the official Adobe website or your organization's software distribution point
  5. 5. Close all instances of Framemaker before running the installer
  6. 6. Run the installer with administrator privileges
  7. 7. After installation, verify the new version by checking Help > About Adobe Framemaker
Caveat Minor: Some legacy document templates or macros may require testing for compatibility with newer versions

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

Fix this in Framemaker Scoped from the published advisory
  • Consultation3.0 h
  • Implementation2.0 h
  • Testing3.0 h
  • Review / QA2.0 h
10.0 hours of engineering $1,770
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,832.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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