CVE-2024-30367
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 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-23013.
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 results from the lack of validating the existence of an object prior to performing operations on it, allowing an attacker to execute arbitrary code in the context of the current process via a malicious PDF file or 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.
-
Verify Foxit PDF software is installedCheck for Foxit PDF Reader or Foxit PDF Editor in your system's installed programs (Control Panel > Programs and Features on Windows, or look in /Applications on macOS). Also check common installation paths such as C:\Program Files\Foxit Software\ on Windows.Affected if Either Foxit PDF Reader or Foxit PDF Editor is present on the system
-
Determine the installed version numberOpen Foxit, then go to Help > About Foxit PDF Reader (or About Foxit PDF Editor). Alternatively, right-click the desktop shortcut and select Properties, then look at the Details tab for the product version.Affected if A version number is displayed that can be compared against the affected ranges
-
Compare your version against affected rangesMatch your installed version/build number to these affected ranges: Reader <= 2023.3.0.23028; Editor <= 10.1.12.37872 OR >= 11.0.0.49893 and <= 11.2.8.53842 OR >= 12.0.0.12394 and <= 12.1.4.15400 OR >= 13.0.0.21632 and <= 13.0.1.21693 OR >= 2023.1.0.15510 and <= 2023.3.0.23028Affected if Your exact version falls within any of these affected ranges
-
Confirm AcroForm feature accessibilityOpen a PDF file in Foxit and check if AcroForm functionality is available. Go to Form tab or check if the software can fill and manage PDF forms.Affected if AcroForm features are accessible and the software version is within the affected ranges
You are affected if Foxit PDF Reader (any version <= 2023.3.0.23028) or Foxit PDF Editor (any version in the specified ranges) is installed, and the AcroForm feature can be used to open or interact with PDF forms.
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 untrusted PDF files or visiting untrusted webpages until the update is applied.
Latest available Foxit PDF Reader/PDF Editor version (newer than 13.0.1.21693 for PDF Editor, newer than 2023.3.0.23028 for PDF Reader)
- 1. Open Foxit PDF Reader or PDF Editor application
- 2. Navigate to Help > Check for Updates or About Foxit to identify current version
- 3. Download the latest version of Foxit PDF Reader or PDF Editor from the official Foxit website (www.foxit.com)
- 4. Close all Foxit applications and any PDF documents
- 5. Run the installer for the latest version
- 6. Follow the installation wizard prompts to complete the upgrade
- 7. After installation, verify the version by checking Help > About Foxit
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation3.0 h
- Implementation6.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 $3,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-30367 — 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-30367 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