CVE-2024-12752
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 Memory Corruption 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 proper validation of user-supplied data, which can result in a memory corruption condition. An attacker can leverage this vulnerability to execute code in the context of the current process. Was ZDI-CAN-25345.
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 memory corruption vulnerability in Foxit PDF Reader's AcroForm handling. The lack of proper validation of user-supplied data during AcroForm processing leads to memory corruption, which a remote attacker can exploit to achieve arbitrary code execution in the context of the current user process.
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.0.0, <= 11.2.11.54113>= 12.0.0, <= 12.1.8.15703>= 13.0.0, <= 13.1.4.23147>= 2023.1.0.15510, <= 2023.3.0.23028>= 2024.1.0.23997, <= 2024.3.0.26795<= 2024.3.0.26795CVSS 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 Windows Registry Editor and navigate to HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall or HKCU\SOFTWARE\Foxit Software. Look for entries named 'Foxit PDF Reader' or 'Foxit Pdf Editor'.Affected if Either Foxit PDF Reader or Foxit PDF Editor is found in the system registry.
-
Determine the installed version numberIn the same registry location, locate the 'DisplayVersion' value for the Foxit installation. Alternatively, right-click the Foxit executable in C:\Program Files\Foxit Software\, select Properties, and check the File Version on the Details tab.Affected if The displayed version falls within any of these ranges: 11.0.0 to 11.2.11.54113, 12.0.0 to 12.1.8.15703, 13.0.0 to 13.1.4.23147, 2023.1.0.15510 to 2023.3.0.23028, 2024.1.0.23997 to 2024.3.0.26795, or any version of Reader <= 2024.3.0.26795.
-
Confirm AcroForm functionality may be usedOpen any PDF file that contains fillable form fields (AcroForm). In Foxit, go to Forms menu or check if form fields are visible and interactive in the document. AcroForm is a standard PDF feature for fillable forms.Affected if PDF documents with fillable forms can be opened and processed by the Foxit installation.
-
Check for automatic PDF rendering in browsersCheck browser extensions or Foxit plugin status. In browser settings (Chrome, Edge, Firefox), look for Foxit PDF extensions or check if PDFs automatically open in Foxit rather than the browser's built-in viewer.Affected if Foxit is set as the default handler for PDF files or has browser extensions enabled for automatic PDF rendering.
If Foxit PDF Reader or Editor is installed and its version falls within the affected ranges listed, and the user can open PDF files with AcroForm content, the environment is potentially affected by this vulnerability.
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.
From vendor dataApply the vendor-supplied patch or update Foxit PDF Reader to the latest version. Until patched, warn users not to open untrusted PDF files or visit malicious web pages that could trigger automatic PDF rendering.
- 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-12752 — 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-12752 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