dbcve.org
Pdf EditorApplication · Foxit

CVE-2024-30361

HIGH · 7.8 CVSS v3.0 Published 2024-04-02
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 AcroForm 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 AcroForms. 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-22877.

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 AcroForm handling. The flaw results from the lack of validating an object's existence before performing operations on it, allowing an attacker to free memory and then access it, leading to remote code execution in the context of the current process.

MitigationUpdate Foxit PDF Reader to the latest version provided by the vendor. Avoid opening untrusted PDF files or visiting malicious pages until the patch is applied.

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. Confirm Foxit PDF software is installed
    Check for Foxit PDF Reader or Foxit PDF Editor in the list of installed programs (Windows: Settings > Apps > Apps & Features, or check Program Files folder for Foxit directory)
    Affected if Either Foxit PDF Reader or Foxit PDF Editor is present on the system
  2. Identify the installed version number
    Open Foxit, click Help > About Foxit PDF Reader/Editor to display the exact version number and build date, or right-click the executable in the installation folder and view Properties > Details
    Affected if The exact version cannot be determined for comparison
  3. Compare version against affected ranges for Foxit PDF Reader
    If Foxit PDF Reader is installed, compare the version to: <= 2023.3.0.63083 or <= 2023.3.0.23028. Note the two different build families
    Affected if The installed version falls within either of these two version constraints
  4. Compare version against affected ranges for Foxit PDF Editor
    If Foxit PDF Editor is installed, compare against these 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.21693; >= 2023.1.0.15510 <= 2023.3.0.23028
    Affected if The installed version matches any of these version ranges
  5. Determine if AcroForm feature is relevant
    AcroForm is a form technology in PDFs. Check if the user works with PDF forms (fillable forms, form templates). This is the component with the vulnerability, but the flaw triggers when processing PDFs regardless of user action
    Affected if The software processes PDF files containing AcroForm objects, which is common in form-enabled PDFs

A user is affected if Foxit PDF Reader or Foxit PDF Editor is installed and the version matches any of the listed vulnerable ranges, especially when opening PDF files that contain AcroForm data.

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 provided by the vendor. Avoid opening untrusted PDF files or visiting malicious pages until the patch is applied.

Recommended fix Moderate confidence

Foxit PDF Reader/PDF Editor 2024.x or later (latest stable release from foxit.com)

  1. 1. Visit the official Foxit website at www.foxit.com to download the latest version of Foxit PDF Reader or PDF Editor.
  2. 2. Identify your current installed version by opening the application, clicking Help > About Foxit PDF Reader (or Editor).
  3. 3. Uninstall the current version of Foxit PDF Reader or PDF Editor from your system.
  4. 4. Download the most recent stable version from the Foxit website that is newer than the vulnerable versions listed (2024.x or later).
  5. 5. Install the downloaded version by running the installer and following the on-screen prompts.
  6. 6. After installation, verify the new version by checking Help > About to confirm the fix is applied.
Caveat Standard upgrade - review release notes for any feature changes between your current version and the new version

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

Fix this in Pdf Editor Scoped from the published advisory
  • Consultation1.0 h
  • Implementation2.0 h
  • Testing1.0 h
  • Review / QA1.0 h
5.0 hours of engineering $890
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,424.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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