CVE-2024-30328
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-22633.
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 confidenceUse-after-free vulnerability in Foxit PDF Reader's AcroForm handling due to lack of validation of Doc object existence before performing operations. An attacker can exploit this by tricking users into opening a malicious PDF, allowing 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 installed Foxit productCheck if Foxit PDF Reader or Foxit PDF Editor is installed. On Windows, look in Program Files for Foxit Software folder, or check registry key HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall for entries starting with Foxit.Affected if No Foxit product is found (not affected)
-
Determine installed Foxit versionOpen Foxit Reader/Editor, go to Help > About, or right-click the application in taskbar and select Properties to view the version number. Alternatively, check the Uninstall registry entry for the DisplayVersion value.Affected if Unable to determine version (unknown)
-
Compare version against affected rangesCompare your installed version number to these ranges: Reader: <= 2023.3.0.63083 or <= 2023.3.0.23028; Editor: <= 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.23028Affected if Version matches any of the affected ranges listed in the CVE
User is affected if Foxit PDF Reader or Foxit PDF Editor version falls within any of the specified vulnerable version ranges.
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 · scopedUpdate Foxit PDF Reader to the latest version; avoid opening PDF files from untrusted sources.
Upgrade to the latest available version of Foxit PDF Reader or PDF Editor (version newer than 2023.3.0.63083 for Pdf Reader and newer than 2023.3.0.63083 for Pdf Editor)
- 1. Open Foxit PDF Reader or PDF Editor application
- 2. Navigate to Help > Check for Updates or About to identify current version
- 3. Download the latest version from the official Foxit website (www.foxit.com)
- 4. Close all Foxit applications
- 5. Run the installer and follow the prompts to upgrade
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation1.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,224.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-30328 — 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-30328 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