dbcve.org
Framemaker Publishing ServerApplication · Adobe

CVE-2024-30300

CRITICAL · 9.8 CVSS v3.1 Published 2024-06-13
Fix available
A fix is available. Upgrade to 2020 or later.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click

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 Publishing Server versions 2020.3, 2022.2 and earlier are affected by an Information Exposure vulnerability (CWE-200) that could lead to privilege escalation. An attacker could exploit this vulnerability to gain access to sensitive information which may include system or user privileges. Exploitation of this issue does not require user interaction.

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 Publishing Server versions 2020.3, 2022.2 and earlier contain an information exposure vulnerability (CWE-200) that allows unauthenticated attackers to access sensitive system or user privilege information, potentially leading to privilege escalation. The flaw requires no user interaction for exploitation.

MitigationUpdate Adobe Framemaker Publishing Server to the latest patched version provided by Adobe's official security bulletin. Review server access logs for indicators of compromise and audit user privilege configurations.

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
Framemaker Publishing ServerApplication
Affected:< 2020= 2020= 2022

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
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/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. Confirm Adobe Framemaker Publishing Server installation
    Locate the product on the system by checking installation directories (typically C:\Program Files\Adobe\ on Windows or /opt/adobe on Linux), running services, or installed programs list.
    Affected if The product is present on the system
  2. Determine installed version
    Find the version number in the application's about panel, version.txt file in the installation directory, or by querying the running service. Compare against the affected versions: 2022.2 and earlier, all 2020.x versions, and any versions before 2020.
    Affected if Installed version is 2022.2 or earlier, 2020.x, or pre-2020
  3. Verify network accessibility
    Check which ports the publishing server is listening on using netstat or similar tools. Determine if these ports are exposed to untrusted networks or the internet.
    Affected if The server is accessible from untrusted network segments
  4. Review server access logs
    Examine the publishing server's access and audit logs for any unauthorized requests, unusual unauthenticated queries, or attempts to access system or user privilege information.
    Affected if Logs show unexplained unauthenticated access or information disclosure requests

The environment is affected if Adobe Framemaker Publishing Server version 2022.2 or earlier, 2020.x, or any version before 2020 is installed and exposed.

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 or later
Fixed in 2020
Interim mitigation

Update Adobe Framemaker Publishing Server to the latest patched version provided by Adobe's official security bulletin. Review server access logs for indicators of compromise and audit user privilege configurations.

Recommended fix Moderate confidence

Upgrade to the latest available Framemaker Publishing Server release (subsequent to 2020.3 and 2022.2) - check Adobe helpx.adobe.com for the specific security update release

  1. Check the currently installed Adobe Framemaker Publishing Server version by accessing the server administration interface or checking the product About information
  2. Navigate to the Adobe Framemaker Publishing Server download page on helpx.adobe.com or the Adobe Creative Cloud desktop application
  3. Download the latest available version of Framemaker Publishing Server (versions subsequent to 2020.3 and 2022.2)
  4. Backup the current server configuration and any custom templates or assets
  5. Stop the Framemaker Publishing Server service before upgrading
  6. Run the installer for the new version and follow the on-screen installation prompts
  7. After installation completes, start the Framemaker Publishing Server service
  8. Verify the server is running correctly and test publishing workflows
Caveat Adobe product updates typically include compatibility changes; review migration documentation and test in a non-production environment before deploying to production

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

Fix this in Framemaker Publishing Server Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,860
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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