CVE-2024-30351
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-22799.
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. The flaw exists because the software fails to validate the existence of Doc objects before performing operations on them, allowing an attacker to potentially control freed memory and achieve arbitrary code execution through malicious PDF files.
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.
-
Confirm Foxit PDF product installationCheck for Foxit PDF Reader or Foxit PDF Editor in installed programs (Windows: Control Panel > Programs and Features, or check C:\Program Files\Foxit or C:\Program Files (x86)\Foxit directories)Affected if Either Foxit PDF Reader or Foxit PDF Editor is installed on the system
-
Locate the Foxit executable versionRight-click the Foxit executable (typically FoxitReader.exe or FoxitPDFEditor.exe), select Properties, and check the Details tab for the File VersionAffected if The executable file version cannot be determined or located
-
Compare installed version against affected rangesCompare your file version to all affected version ranges: <= 11.1.6.0109; >= 12.0.0.0601 to <= 12.1.2.55366; >= 13.0.0.61829 to <= 13.0.1.61866; >= 2023.1.0.55583 to <= 2023.3.0.63083; <= 10.1.12.37872; >= 11.0.0.49893 to <= 11.2.8.53842; >= 12.0.0.12394 to <= 12.1.4.15400; >= 13.0.0.21632 to <= 13.0.1.21693; >= 2023.1.0.15510 to <= 2023.3.0.23028 (for Editor) or <= 2023.3.0.63083 and <= 2023.3.0.23028 (for Reader)Affected if Your installed version falls within any of the listed affected version ranges or is lower than the highest listed affected version (2023.3.0.63083 for Reader, 13.0.1.61866 for Editor)
-
Check for AcroForm feature usage exposureOpen a PDF with AcroForm fields (check Document Properties in Foxit under Forms, or attempt to open a PDF that uses fillable form fields)Affected if AcroForm functionality is accessible or used, as the vulnerability specifically targets AcroForm handling
You are affected if Foxit PDF Reader or Foxit PDF Editor is installed with a version number matching any of the affected ranges listed in the CVE (versions up to and including 2023.3.0.63083 for Reader, or various ranges up to 13.0.1.61866 for Editor).
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 dataApply the vendor-supplied patch by updating Foxit PDF Reader to the latest version. Users should avoid opening PDF files from untrusted sources until the patch is applied.
- Consultation4.0 h
- Implementation8.0 h
- Testing4.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 $5,120.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-30351 — 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-30351 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