Pdf EditorApplication · Foxit

CVE-2024-7724

HIGH · 8.8 CVSS v3.1 Published 2024-08-21
Fix available
A fix is available. Upgrade to 11.2.11.54113 / 12.1.8.15703 or later.
See remediation →
95/100
Remediation priority · Urgent
Remotely reachable 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 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-23900.

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

A use-after-free vulnerability in Foxit PDF Reader's AcroForm handling allows remote attackers to execute arbitrary code by convincing users to open malicious PDF files. The flaw stems from the lack of validating object existence before performing operations on them, leading to memory corruption that can be leveraged for code execution in the context of the current process.

MitigationOrganizations should update Foxit PDF Reader to the latest patched version once available, and users should be trained to avoid opening untrusted PDF files. Consider disabling JavaScript execution in Foxit Reader to reduce the 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.2.11.54113>= 12.0.0.12394, < 12.1.8.15703>= 13.0.0.21632, < 13.1.3.22478>= 2023.1.0.15510, < 2024.2.3.25184
Pdf ReaderApplication
Affected:< 2024.2.3.25184

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
Network
Complexity
Low
Privileges
None
User interaction
Required
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/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
    Check installed programs for Foxit PDF Reader or Foxit Pdf Editor. In Windows, open Control Panel > Programs and Features or check Add/Remove Programs. The product name will indicate whether you have Reader or Editor.
    Affected if Foxit Pdf Reader or Foxit Pdf Editor is installed
  2. Determine installed Foxit version
    In Foxit, click Help > About Foxit PDF Reader/Editor. Alternatively, right-click the Foxit icon, select Properties, and check the version in the Details tab. Record the full version number including build number.
    Affected if Version number cannot be determined or is not visible
  3. Compare version against affected ranges
    Match your installed version to these affected ranges: For Reader: < 2024.2.3.25184. For Editor: < 11.2.11.54113; >= 12.0.0.12394, < 12.1.8.15703; >= 13.0.0.21632, < 13.1.3.22478; >= 2023.1.0.15510, < 2024.2.3.25184
    Affected if Installed version falls within any of the affected ranges listed
  4. Verify AcroForm functionality status
    In Foxit PDF, go to File > Preferences > Forms. Check if AcroForm functionality is enabled. On some versions, AcroForm is enabled by default when opening PDFs.
    Affected if AcroForms are enabled (the exploit cannot trigger if this feature is completely disabled)
  5. Assess user interaction exposure
    Review organizational practices for opening PDF files from untrusted or external sources. The vulnerability requires a user to open a maliciously crafted PDF file.
    Affected if Users routinely open PDF attachments from unknown or untrusted sources

You are affected if you have Foxit PDF Reader or Foxit Pdf Editor installed with a version number that falls within the affected ranges AND users can open untrusted PDF files with AcroForms enabled.

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 11.2.11.54113 / 12.1.8.15703 / 13.1.3.22478 or later
Fixed in 11.2.11.5411312.1.8.1570313.1.3.22478
Interim mitigation

Organizations should update Foxit PDF Reader to the latest patched version once available, and users should be trained to avoid opening untrusted PDF files. Consider disabling JavaScript execution in Foxit Reader to reduce the attack surface.

Recommended fix High confidence

Pdf Editor: 11.2.11.54113 (for v11), 12.1.8.15703 (for v12), 13.1.3.22478 (for v13), or 2024.2.3.25184 (for v2023/2024) | Pdf Reader: 2024.2.3.25184

  1. 1. Identify the currently installed Foxit PDF product (Pdf Reader or Pdf Editor) and its exact version number
  2. 2. Based on your current version, determine the minimum fixed version needed: For Pdf Editor versions <11.2.11.54113 upgrade to 11.2.11.54113 or later; For Pdf Editor 12.x versions (>=12.0.0.12394 and <12.1.8.15703) upgrade to 12.1.8.15703 or later; For Pdf Editor 13.x versions (>=13.0.0.21632 and <13.1.3.22478) upgrade to 13.1.3.22478 or later; For Pdf Editor 2023.x/2024.x versions (>=2023.1.0.15
  3. 3. For Pdf Reader (any version <2024.2.3.25184), upgrade to version 2024.2.3.25184 or later
  4. 4. Download the updated version from the official Foxit website at www.foxit.com
  5. 5. Close all Foxit applications before running the installer
  6. 6. Run the installer with elevated privileges and follow the prompts to complete the upgrade
  7. 7. After installation, verify the version number in Help > About Foxit PDF Reader/Editor confirms the new version
Caveat Standard upgrade within same major version should have minimal risk; users on very old versions may need to review plugin/extension compatibility

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
  • Implementation2.0 h
  • Testing3.0 h
  • Review / QA1.0 h
8.0 hours of engineering $1,390
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,224.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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