CVE-2024-30365
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 · uneditedFoxit 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-22947.
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 confidenceA use-after-free vulnerability exists in Foxit PDF Reader's AcroForms handling. The code fails to validate that an object exists before performing operations on it, leading to a memory safety flaw that can be exploited to achieve arbitrary code execution in the context of the current process.
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<= 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<= 2023.3.0.63083<= 2023.3.0.23028CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Identify if Foxit PDF Reader or Editor is installedOpen the application and go to Help > About, or check Add/Remove Programs on Windows or Applications folder on macOS for installed Foxit softwareAffected if Foxit PDF Reader or Foxit PDF Editor is present on the system
-
Determine the installed version numberIn the application, navigate to Help > About Foxit PDF Reader/Editor. Note the exact version string displayed (for example, 2023.3.0.63083 or 13.0.1.21693)Affected if The version matches any of the affected ranges provided in the CVE advisory
-
Confirm the product typeVerify whether the installed application is Foxit PDF Reader specifically or Foxit PDF Editor, as version ranges differ between these two productsAffected if The product is Foxit PDF Reader with version <= 2023.3.0.63083 or <= 2023.3.0.23028, or Foxit PDF Editor with any of the multiple affected version ranges listed
-
Verify AcroForms are being processedOpen any PDF files that contain AcroForms (form fields) to trigger the vulnerable AcroForms handling code path. PDFs with interactive forms will exercise this functionalityAffected if PDFs containing AcroForms are opened or processed by the vulnerable version
You are affected if Foxit PDF Reader or Foxit PDF Editor is installed with a version matching any of the CVE-listed affected ranges and AcroForm-containing PDFs are opened.
Generated from the published advisory. Verify against your own configuration.
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 · scopedApply the vendor-supplied security patch for Foxit PDF Reader. Ensure all users update to the latest patched version to remediate this vulnerability.
Latest available Foxit PDF Reader/PDF Editor 2024.x or later release (versions greater than 2023.3.0.63083)
- 1. Visit the official Foxit website at www.foxit.com to download the latest version of Foxit PDF Reader or PDF Editor
- 2. Identify your current product version by clicking Help > About Foxit PDF Reader (or PDF Editor)
- 3. Download the most recent version available (2024.x or later)
- 4. Close all Foxit applications
- 5. Run the installer and follow the prompts to upgrade
- 6. After installation, verify the new version in Help > About to confirm the upgrade was successful
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation4.0 h
- Testing2.0 h
- Review / QA1.0 h
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 locallyCheck whether your project pulls in CVE-2024-30365 — 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 sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2024-30365 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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