CVE-2024-30346
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-22745.
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 confidenceThis is a use-after-free vulnerability in Foxit PDF Reader's AcroForm handling, specifically in Doc object processing. The flaw results from the lack of validating an object's existence prior to performing operations on it, allowing an attacker to free memory and then reuse it, leading to 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 installedCheck for Foxit application in typical installation locations (C:\Program Files\Foxit Software\ or C:\Program Files (x86)\Foxit Software\) or look for Foxit entries in Windows Registry under HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\UninstallAffected if Foxit PDF Reader or Foxit PDF Editor is present on the system
-
Locate the Foxit executable and get its versionRight-click the Foxit executable (e.g., FoxitReader.exe or FoxitPDFEditor.exe), select Properties, and check the Details tab for Product Version. Alternatively, run: Get-Item 'C:\Program Files\Foxit Software\Foxit PDF Reader\FoxitReader.exe' | Select-Object VersionInfoAffected if The executable exists and returns a version number
-
Compare installed version against affected rangesMatch your installed version number to these affected ranges: For Foxit PDF Editor: <= 11.1.6.0109; >= 12.0.0.0601 through <= 12.1.2.55366; >= 13.0.0.61829 through <= 13.0.1.61866; >= 2023.1.0.55583 through <= 2023.3.0.63083; <= 10.1.12.37872; >= 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. For Foxit PDF Reader: <= 2023.3.0.63083 or <= 2023.3.0.23028Affected if The installed version falls within any of these affected ranges
-
Confirm AcroForm handling capability is in useThe vulnerability triggers when processing PDFs containing AcroForm fields. Check if the installed Foxit version has PDF form functionality enabled by opening a PDF with form fields or checking Help > About for form-related modules. The vulnerability applies when opening any PDF with AcroForm contentAffected if The user opens or processes PDF files containing AcroForm fields
You are affected if Foxit PDF Reader or Foxit PDF Editor is installed with a version matching the affected ranges and you open PDF files containing AcroForm fields.
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 version once the vendor releases a patch. Until then, avoid opening untrusted PDF files and restrict user access to malicious pages.
- Consultation1.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,200.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-30346 — 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-30346 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