CVE-2024-9252
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 Information Disclosure Vulnerability. This vulnerability allows remote attackers to disclose sensitive information 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 in conjunction with other vulnerabilities to execute arbitrary code in the context of the current process. Was ZDI-CAN-24491.
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 · moderate confidenceA use-after-free vulnerability in Foxit PDF Reader's AcroForm handling allows attackers to access freed memory objects due to insufficient validation of object existence before operations. This can leak sensitive information and, when combined with other vulnerabilities, enable 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<= 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.
-
Locate Foxit PDF applicationSearch for Foxit PDF Reader or Foxit PDF Editor executable in typical installation paths: C:\Program Files\Foxit Software\ or C:\Program Files (x86)\Foxit Software\. Check Start Menu shortcuts or Control Panel Programs and Features.Affected if Foxit PDF Reader or Foxit PDF Editor is installed on the system
-
Determine installed versionRight-click the Foxit executable (e.g., FoxitReader.exe or FoxitPDFEditor.exe), select Properties, then view the Details tab to find the Product Version field.Affected if The version number 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 Reader: <= 2024.2.3.25184)
-
Confirm AcroForm feature is in useOpen a PDF file that contains AcroForm fields (check Document Properties in Foxit under the Forms tab). AcroForm is a standard PDF feature and is typically enabled by default when opening forms-based PDFs.Affected if The user opens or interacts with PDF files containing AcroForm fields while using a vulnerable Foxit version
The environment is affected if Foxit PDF Reader or Foxit PDF Editor is installed with a version number within the affected ranges AND the user opens PDF files containing 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 · scopedUpdate Foxit PDF Reader to the vendor's latest version when available; avoid opening untrusted PDF files or visiting malicious web pages until the patch is applied.
Foxit PDF Reader 2024.2.3.25184 or later; Foxit PDF Editor versions greater than 11.2.10.53951, 12.1.7.15526, 13.1.3.22478, and 2023.3.0.23028
- 1. Visit the official Foxit software update page or check for updates within the Foxit PDF Reader/PDF Editor application.
- 2. Download and install the latest version of Foxit PDF Reader or PDF Editor from the official Foxit website (www.foxit.com).
- 3. Verify the installed version matches or exceeds the fixed release for your product line.
- 4. For enterprise deployments, use Foxit's enterprise deployment tools to push the update to all affected systems.
- 5. Confirm the update was successfully applied by checking the software version in Help > About.
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation2.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 $1,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-9252 — 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-9252 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