CVE-2024-30333
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 Doc Object 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-22639.
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 Doc object handling. The flaw results from the lack of validating the existence of an object prior to performing operations on it, allowing an attacker to potentially execute arbitrary code in the context of the current process by tricking users into opening a malicious PDF file or visiting a malicious webpage.
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.
-
Identify installed Foxit productCheck Programs and Features (Windows) or Applications folder (Mac) for Foxit PDF Reader or Foxit PDF Editor. Alternatively, launch the application and check Help > About to confirm which product is installed.Affected if Either Foxit PDF Reader or Foxit PDF Editor is present on the system
-
Determine installed version of Foxit PDF ReaderIn Foxit PDF Reader, go to Help > About Foxit Reader or right-click the executable and select Properties > Details to view the version number.Affected if The version is < 2023.3.0.23028
-
Determine installed version of Foxit PDF EditorIn Foxit PDF Editor, go to Help > About Foxit PDF Editor or right-click the executable and select Properties > Details to view the version number.Affected if The version falls into any of these ranges: < 10.1.12.37872; >= 11.0.0.49893 and < 11.2.8.53842; >= 12.0.0.12394 and < 12.1.4.15400; >= 13.0.0.21632 and < 13.0.1.21693; >= 2023.1.0.15510 and < 2023.3.0.23028
-
Assess user interaction riskConsider whether the system routinely opens PDF files from untrusted sources or visits untrusted websites that could deliver malicious PDF content.Affected if Users on this system open PDF files from unknown sources or browse to untrusted websites that could host malicious PDFs
You are affected if Foxit PDF Reader version < 2023.3.0.23028 or Foxit PDF Editor version matching any of the vulnerable version ranges is installed, and users could open untrusted PDF files or visit malicious webpages.
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 · scoped10.1.12.3787211.2.8.5384212.1.4.15400
Apply the vendor patch from Foxit when available; until then, enforce user awareness to avoid opening untrusted PDF files and visiting untrusted websites, and consider network/email filtering to block suspicious PDF attachments.
Pdf Editor: 10.1.12.37872 (v10), 11.2.8.53842 (v11), 12.1.4.15400 (v12), 13.0.1.21693 (v13) | Pdf Reader: 2023.3.0.23028
- 1. Open Foxit PDF Reader or PDF Editor
- 2. Click on Help > About Foxit PDF Reader (or About Foxit PDF Editor) to check the current version number
- 3. Identify your product and current version from the affected versions list
- 4. Visit the official Foxit website at www.foxit.com to download the latest version
- 5. For Pdf Editor: upgrade to version 10.1.12.37872 or higher for version 10.x; upgrade to version 11.2.8.53842 or higher for version 11.x; upgrade to version 12.1.4.15400 or higher for version 12.x; upgrade to version 13.0.1.21693 or higher for version 13.x
- 6. For Pdf Reader: upgrade to version 2023.3.0.23028 or higher
- 7. Download and install the appropriate fixed version
- 8. Restart the application after installation
Generated from the published advisory — verify against the referenced sources before acting.
- 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-30333 — 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-30333 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