Pdf EditorApplication · Foxit

CVE-2024-30371

HIGH · 7.8 CVSS v3.0 Published 2024-04-02
Fix available
A fix is available. Upgrade to after 2023.3.0.23028 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-23355.

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

This is a use-after-free vulnerability in Foxit PDF Reader's AcroForm handling. The vulnerability stems from the lack of validation that an object exists before performing operations on it, allowing an attacker to manipulate memory and execute arbitrary code in the context of the current process when a user opens a malicious PDF.

MitigationUpdate Foxit PDF Reader to the latest version. Avoid opening PDF files from untrusted sources and disable JavaScript execution in PDF reader settings as a defense-in-depth measure.

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:<= 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.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. Locate Foxit PDF Reader installation
    Search for the Foxit PDF Reader executable (FoxitReader.exe) in common installation directories such as C:\Program Files\Foxit Software\Foxit PDF Reader\ or C:\Program Files (x86)\Foxit Software\Foxit PDF Reader\. Alternatively, open Command Prompt and run where FoxitReader.exe to find the installed path.
    Affected if Foxit PDF Reader is not found on the system, then this CVE does not apply.
  2. Retrieve installed version number
    Right-click on FoxitReader.exe, select Properties, then go to the Details tab and read the Product version field. Alternatively, open Foxit PDF Reader, click Help > About Foxit Reader to display the version dialog.
    Affected if The version cannot be determined, treat it as unknown and proceed with caution.
  3. Compare version against affected ranges
    Compare your installed version to the following affected ranges: versions <= 2023.3.0.23028. If your version falls within any of these ranges, your installation is affected: 10.1.12.37872 and below; 11.0.0.49893 through 11.2.8.53842; 12.0.0.12394 through 12.1.4.15400; 13.0.0.21632 through 13.0.1.21693; 2023.1.0.15510 through 2023.3.0.23028.
    Affected if Your installed version matches or falls within any of the listed affected version ranges.
  4. Confirm AcroForm handling is reachable
    The vulnerability exists in the AcroForm handling component. This feature is part of standard PDF functionality and is automatically available when opening PDF files that contain AcroForm fields. No specific configuration toggle exists to disable this component.
    Affected if The installed version is within the affected ranges and you open PDF files that may contain AcroForm content.

You are affected if Foxit PDF Reader is installed and its version falls within the <= 2023.3.0.23028 range, as all versions up to and including 2023.3.0.23028 are impacted by this use-after-free vulnerability in AcroForm handling.

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.23028
Interim mitigation

Update Foxit PDF Reader to the latest version. Avoid opening PDF files from untrusted sources and disable JavaScript execution in PDF reader settings as a defense-in-depth measure.

Recommended fix High confidence

Foxit PDF Reader/Editor latest version (verify version > 13.0.1.21693 for Editor, > 2023.3.0.23028 for Reader)

  1. 1. Identify the currently installed Foxit PDF product (Reader or Editor) and its exact version number from the Help > About menu
  2. 2. For Foxit PDF Reader users: Navigate to the official Foxit download page at https://www.foxit.com/downloads/ and download the latest version
  3. 3. For Foxit PDF Editor users: Navigate to https://www.foxit.com/downloads/pdf-editor/ and download the latest version matching your license type (Standard or Pro)
  4. 4. Uninstall the current version through Windows Control Panel > Programs and Features
  5. 5. Install the newly downloaded version, ensuring you uncheck any optional bundled software during installation
  6. 6. Verify the installation was successful by checking Help > About to confirm the version is newer than the vulnerable releases
  7. 7. Restart any running Foxit instances and ensure the application launches without errors
Caveat Ensure compatibility with existing PDF files and any integrated plugins; the latest major version should maintain full backward compatibility

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
  • Implementation4.0 h
  • Testing2.0 h
  • Review / QA1.0 h
9.0 hours of engineering $1,600
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,560.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2024-30371 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