CVE-2024-30352
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. 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-22800.
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 Doc object handling. The lack of validating object existence before performing operations leads to memory corruption that can be leveraged for arbitrary code execution in the current process context.
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<= 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.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.
-
Check if Foxit PDF Reader or Editor is installedOpen Programs and Features (appwiz.cpl) or check the installation directory (typically C:\Program Files\Foxit Software\) for Foxit PDF Reader.exe or Foxit PDF Editor.exeAffected if Either Foxit PDF Reader or Foxit PDF Editor executable exists on the system
-
Determine the installed Foxit PDF versionRight-click on FoxitPDF Reader.exe or FoxitPDF Editor.exe in the installation folder, select Properties, then go to the Details tab and note the File Version valueAffected if The version number cannot be determined or the file does not exist
-
Compare Reader version against affected rangeIf using Foxit PDF Reader, compare the installed version to the affected range: any version <= 2023.3.0.23028 is affectedAffected if The installed Foxit PDF Reader version is 2023.3.0.23028 or lower
-
Compare Editor version against affected rangesIf using Foxit PDF Editor, compare the installed version against all affected ranges: <= 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.23028Affected if The installed Foxit PDF Editor version falls within any of the listed affected ranges
If Foxit PDF Reader version is 2023.3.0.23028 or lower, or Foxit PDF Editor version falls within any of the specified affected ranges, the environment is vulnerable to CVE-2024-30352.
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 vendor patch by updating Foxit PDF Reader to the latest version; avoid opening untrusted PDF files or visiting malicious pages until patched.
Foxit PDF Reader 2024.x or later; Foxit PDF Editor: latest version (14.x recommended)
- 1. Identify the currently installed Foxit PDF Reader or PDF Editor version by opening the application and navigating to Help > About Foxit PDF Reader/Editor
- 2. For Foxit PDF Reader: Upgrade to a version newer than 2023.3.0.23028 (e.g., 2024.x release)
- 3. For Foxit PDF Editor: Based on your current major version, upgrade to a release higher than your current vulnerable version: 10.x users should upgrade beyond 10.1.12.37872; 11.x users should upgrade beyond 11.2.8.53842; 12.x users should upgrade beyond 12.1.4.15400; 13.x users should upgrade beyond 13.1.1.21693
- 4. Download the latest version from the official Foxit website at https://www.foxit.com/downloads/
- 5. Close all Foxit applications before installing the update
- 6. Run the installer and follow the prompts to complete the upgrade
- 7. After installation, verify the new version in Help > About to confirm the patch was applied
- 8. Do not open untrusted or unexpected PDF files from untrusted sources, as user interaction is required for exploitation
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation3.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,272.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-30352 — 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-30352 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