dbcve.org
Pdf EditorApplication · Foxit

CVE-2024-30327

HIGH · 7.8 CVSS v3.0 Published 2024-04-03
Fix available
A fix is available. Upgrade to after 2023.3.0.63083 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
Foxit PDF Reader template Use-After-Free Remote Code Execution Vulnerability. This vulnerability allows remote attackers to execute arbitrary code on affected installations of Foxit PDF Reader. User interaction is required to exploit this vulnerability in that the target must visit a malicious page or open a malicious file. The specific flaw exists within the handling of template objects. The issue results from the lack of validating the existence of an object prior to performing operations on the object. An attacker can leverage this vulnerability to execute code in the context of the current process. Was ZDI-CAN-22632.

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

A Use-After-Free vulnerability exists in Foxit PDF Reader's template object handling. The flaw results from failing to validate object existence before performing operations on template objects, allowing an attacker to manipulate freed memory and achieve arbitrary code execution within the current process context.

MitigationUpdate Foxit PDF Reader to the latest version containing the security patch. Until patched, exercise caution with untrusted PDF files and avoid opening them in Foxit Reader.

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
Pdf EditorApplication
Affected:<= 11.1.6.0109>= 12.0.0.0601, <= 12.1.2.55366>= 13.0.0.61829, <= 13.0.1.61866>= 2023.1.0.55583, <= 2023.3.0.63083<= 10.1.12.37872>= 11.0.0.49893, <= 11.2.8.53842>= 12.0.0.12394, <= 12.1.4.15400>= 13.0.0.21632, <= 13.0.1.21693>= 2023.1.0.15510, <= 2023.3.0.23028
Pdf ReaderApplication
Affected:<= 2023.3.0.63083<= 2023.3.0.23028

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.0/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 if Foxit PDF Reader is installed
    Open Windows Settings > Apps > Installed Apps (or use Control Panel > Programs and Features) and look for 'Foxit PDF Reader' in the application list
    Affected if Foxit PDF Reader appears in the installed programs list
  2. Determine the installed Foxit PDF Reader version
    In the Apps list, click on Foxit PDF Reader, then select 'Advanced' to view the version, or right-click the desktop shortcut and choose 'Properties' to view the version under the 'Details' tab
    Affected if The version displayed matches any of these vulnerable ranges: <= 2023.3.0.63083 or <= 2023.3.0.23028
  3. Check if Foxit PDF Editor is installed
    Look in Windows Settings > Apps > Installed Apps (or Control Panel > Programs and Features) for 'Foxit PDF Editor' or 'Foxit PhantomPDF'
    Affected if Foxit PDF Editor appears in the installed programs list
  4. Determine the installed Foxit PDF Editor version
    Click on Foxit PDF Editor in the Apps list and view version details, or right-click the application shortcut and check the 'Details' tab in Properties for the version number
    Affected if The version displayed falls within any of these vulnerable ranges: <= 11.1.6.0109; >= 12.0.0.0601, <= 12.1.2.55366; >= 13.0.0.61829, <= 13.0.1.61866; >= 2023.1.0.55583, <= 2023.3.0.63083; <= 10.1.12.37872; >= 11.0.0.49893, <= 11.2.8.53842; >= 12.0.0.12394, <= 12.1.4.15400; >= 13.0.0.21632, <= 13.0.1
  5. Assess exposure to untrusted PDF files
    Check if the Foxit application is configured to automatically open PDF files from email attachments, web downloads, or network shares without user confirmation
    Affected if The software opens PDFs automatically from untrusted sources, increasing the likelihood of encountering a malicious PDF that exploits this vulnerability

You are affected if Foxit PDF Reader or Foxit PDF Editor is installed and its version matches any of the listed vulnerable ranges, especially if the application routinely opens PDF 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 a release after 2023.3.0.63083
Interim mitigation

Update Foxit PDF Reader to the latest version containing the security patch. Until patched, exercise caution with untrusted PDF files and avoid opening them in Foxit Reader.

Recommended fix Moderate confidence

Latest available version of Foxit PDF Reader or PDF Editor (vendor should be contacted for specific fixed version numbers)

  1. 1. Identify the exact Foxit product installed (PDF Reader or PDF Editor) and note the current version number from Help > About
  2. 2. For PDF Reader: Navigate to Foxit.com > Products > Foxit Reader > Download and install the latest version available
  3. 3. For PDF Editor: Navigate to Foxit.com > Products > Foxit PDF Editor > Download and install the latest version available
  4. 4. Alternatively, use the built-in updater: Go to Help > Check for Updates and follow prompts to install the latest version
  5. 5. Restart the application after updating
  6. 6. Verify the new version by checking Help > About
Caveat Minor: Some legacy PDF features or plugins may need reconfiguration after major version upgrades

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

Fix this in Pdf Editor Scoped from the published advisory
  • Consultation2.0 h
  • Implementation1.0 h
  • Testing2.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,060
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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