Pdf EditorApplication · Foxit

CVE-2024-12751

HIGH · 7.8 CVSS v3.0 Published 2024-12-30
Fix available
A fix is available. Upgrade to after 2024.3.0.26795 or later.
See remediation →
81/100
Remediation priority · High
No privileges

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 · unedited
Foxit PDF Reader AcroForm Out-Of-Bounds Read 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 read past the end of an allocated buffer. An attacker can leverage this vulnerability to execute code in the context of the current process. Was ZDI-CAN-25344.

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 confidence

This is an out-of-bounds read vulnerability in Foxit PDF Reader's AcroForm handling component. The lack of proper validation of user-supplied data allows reading past the end of an allocated buffer, which can be leveraged to execute arbitrary code in the context of the current process. Exploitation requires user interaction via a malicious page or file.

MitigationUpdate Foxit PDF Reader to the vendor-patched version when available; until then, avoid opening untrusted PDF files and disable JavaScript execution in PDF settings to reduce attack surface.

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
Pdf EditorApplication
Affected:>= 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
Pdf ReaderApplication
Affected:<= 2024.3.0.26795

CVSS 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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify installed Foxit product
    Open Windows Settings > Apps > Installed apps and search for 'Foxit', or check Program Files for Foxit Software folder, or query registry key HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall for DisplayName containing 'Foxit'
    Affected if Foxit PDF Reader or Foxit PDF Editor is installed
  2. Get installed version number
    Right-click the Foxit executable (e.g., FoxitReader.exe in the installation folder), select Properties, go to Details tab, and note the 'Product version' field; alternatively, check registry at HKLM\SOFTWARE\Foxit Software\Foxit Reader\Install or view version in Help > About Foxit within the application
    Affected if 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 for Reader any version up to 2024.3.0.26795
  3. Confirm AcroForm handling is active
    This vulnerability affects the AcroForm handling component which processes PDF form fields automatically; no explicit user configuration needed as AcroForm support is built into Foxit's PDF rendering engine
    Affected if The software loads or displays any PDF file containing AcroForm form fields, which is a standard PDF feature
  4. Locate Foxit installation path
    Check C:\Program Files\Foxit Software\ or C:\Program Files (x86)\Foxit Software\ for the Foxit installation directory, or use command: dir /s /b 'C:\Program Files\Foxit*' and dir /s /b 'C:\Program Files (x86)\Foxit*'
    Affected if Foxit software is installed in standard or non-standard locations

A user is affected if Foxit PDF Reader or Foxit PDF Editor is installed with a version number within the affected ranges (all versions up to 2024.3.0.26795 for Reader, or the specific ranges listed for Editor) and the application processes PDF files with AcroForm content.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 · scoped
Upgrade available Upgrade to a release after 2024.3.0.26795
Interim mitigation

Update Foxit PDF Reader to the vendor-patched version when available; until then, avoid opening untrusted PDF files and disable JavaScript execution in PDF settings to reduce attack surface.

Recommended fix Moderate confidence

Foxit PDF Reader: 2024.3.0.26795 or later (latest available); Foxit PDF Editor: latest version beyond 11.2.11.54113, 12.1.8.15703, 13.1.4.23147, or 2023.3.0.23028

  1. 1. Identify the exact Foxit product installed (PDF Reader or PDF Editor) and its current version by opening the application and navigating to Help > About
  2. 2. For Foxit PDF Reader: Visit the official Foxit website download page or check Help > Check for Updates to obtain the latest version
  3. 3. For Foxit PDF Editor: Visit the official Foxit website download page or check Help > Check for Updates to obtain the latest version
  4. 4. Download the latest version that addresses CVE-2024-12751 (version higher than the vulnerable releases)
  5. 5. Close all Foxit applications and any PDF files currently open
  6. 6. Run the installer for the updated version and follow the prompts to complete the installation
  7. 7. After installation, verify the new version by checking Help > About to confirm the patch was applied
Caveat Standard upgrade - review release notes for any feature changes or migration notes specific to your version

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Pdf Editor Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing2.0 h
  • Review / QA1.0 h
9.0 hours of engineering $1,600
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,560.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-12751 — 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 sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2024-12751 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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