CVE-2024-9250
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-24489.
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 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.2.10.53951>= 12.0, <= 12.1.7.15526>= 13.0, <= 13.1.3.22478>= 2023.0, <= 2023.3.0.23028>= 2024.0, <= 2024.2.3.25184<= 2024.2.3.25184CVSS 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.1/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 productOpen Foxit PDF Reader or Foxit PDF Editor and navigate to Help > About, or check Programs and Features in Control Panel for installed Foxit applicationsAffected if The system has Foxit PDF Reader or Foxit PDF Editor installed
-
Determine installed version numberIn Foxit, go to Help > About to view the exact version (for example: 11.2.10.x, 12.1.7.x, 13.1.3.x, 2023.3.0.x, or 2024.2.3.x)Affected if The displayed version falls within any of these ranges: <= 11.2.10.53951; >= 12.0 and <= 12.1.7.15526; >= 13.0 and <= 13.1.3.22478; >= 2023.0 and <= 2023.3.0.23028; >= 2024.0 and <= 2024.2.3.25184 (for Editor), or <= 2024.2.3.25184 (for Reader)
-
Verify AcroForm feature is accessibleOpen any PDF in Foxit and check if AcroForm functionality is available (File > Properties > Forms, or attempt to interact with form fields in a PDF)Affected if AcroForm features are present and usable in the installed Foxit application
-
Confirm application handles PDF files with formsCheck whether the user regularly opens PDF documents containing AcroForm fields (common in fillable forms, government documents, or business forms)Affected if The user opens or processes PDF files that may contain AcroForm content from untrusted sources
The environment is affected if Foxit PDF Reader version is <= 2024.2.3.25184 OR Foxit PDF Editor version is within any of the listed vulnerable version ranges, and the user opens PDF files with AcroForm content.
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 · scopedUsers should avoid opening untrusted PDF files and ensure Foxit PDF Reader is updated to the latest patched version. Disable JavaScript execution in PDF reader settings as an additional hardening measure.
Foxit PDF Reader 2024.2.4 or later; Foxit PDF Editor 11.2.11 or later, 12.1.8 or later, 13.1.4 or later, 2023.3.1 or later
- 1. Open Foxit PDF Reader or PDF Editor application
- 2. Navigate to Help > Check for Updates (or About > Check for Updates)
- 3. If an update is available, download and install the latest version
- 4. Alternatively, download the latest version from the official Foxit website at www.foxit.com
- 5. Restart the application after installation
- 6. Verify the version by checking Help > About to confirm you are running a version newer than the affected releases
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-9250 — 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-9250 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