CVE-2024-30336
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 Doc objects in 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-22642.
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 in Foxit PDF Reader's AcroForms handling allows remote code execution through manipulation of Doc objects. The flaw exists due to lack of validation of object existence before performing operations on them, leading to dangling pointer exploitation when the memory is freed but still referenced.
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, <= 12.1.2.55366>= 13.0.0, <= 13.0.1.61866>= 2023.1.0.55583, <= 2023.3.0.63083<= 11.2.8.53842>= 12.0.0, <= 12.1.4.15400>= 2023.1.0.15510, <= 2023.3.0.63083<= 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 installed Foxit PDF applicationOpen the Foxit application and navigate to Help > About Foxit PDF Reader (or About Foxit PDF Editor). Alternatively, check Programs and Features in Control Panel for the installed Foxit product and version.Affected if The product listed is Foxit PDF Reader or Foxit PDF Editor.
-
Confirm the exact version numberLocate the full version string displayed in the About dialog (for example: 11.1.6.0109, 12.1.2.55366, 13.0.1.61866, 2023.3.0.63083). Record the complete version number including build numbers.Affected if The version cannot be determined or the application is not Foxit PDF Reader/Editor.
-
Compare version against affected rangesFor Foxit PDF Editor: check if version is <= 11.1.6.0109; OR >= 12.0.0 AND <= 12.1.2.55366; OR >= 13.0.0 AND <= 13.0.1.61866; OR >= 2023.1.0.55583 AND <= 2023.3.0.63083; OR <= 11.2.8.53842; OR >= 12.0.0 AND <= 12.1.4.15400; OR >= 2023.1.0.15510 AND <= 2023.3.0.63083. For Foxit PDF Reader: check if version is <= 2023.3.0.63083 OR <= 2023.3.0.23028.Affected if The installed version falls within any of the listed affected version ranges.
-
Verify PDF handling configurationOpen Foxit and navigate to File > Preferences > General to review PDF handling settings. Confirm whether PDF files with AcroForms are processed (AcroForms are standard PDF form objects).Affected if The application processes PDF files with AcroForms features.
You are affected if Foxit PDF Reader or Foxit PDF Editor is installed and the version number falls within any of the specified affected ranges (multiple version windows across 11.x, 12.x, 13.x, and 2023.x releases).
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.
From vendor dataUpdate Foxit PDF Reader to the latest vendor patch. Until patched, avoid opening PDF files from untrusted sources and disable JavaScript execution in PDF settings as a defense-in-depth measure.
- Consultation1.0 h
- Implementation2.0 h
- Testing1.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 $1,424.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-30336 — 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-30336 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