dbcve.org
Pdf EditorApplication · Foxit

CVE-2024-7723

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-23736.

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 a use-after-free vulnerability in Foxit PDF Reader's AcroForm handling. The flaw allows remote code execution because the software fails to validate object existence before performing operations, leading to a Use-After-Free condition that can be exploited to execute arbitrary code in the context of the current process.

MitigationApply the vendor security update from Foxit when available. Until then, avoid opening untrusted PDF files and disable JavaScript execution in PDF Reader as a defense-in-depth measure.

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. Check if Foxit PDF Reader is installed
    On Windows, look in C:\Program Files\Foxit Software\ or C:\Program Files (x86)\Foxit Software\ for Foxit Reader. On macOS, check /Applications for Foxit Reader.app. Alternatively, search for 'Foxit Reader' in the system search.
    Affected if Foxit PDF Reader is found on the system
  2. Determine Foxit PDF Reader version
    Open Foxit Reader, then go to Help > About Foxit Reader to display the exact version number. Alternatively, right-click the FoxitReader.exe file in the installation folder, select Properties, and check the Details tab for the Product Version.
    Affected if The installed version is lower than 2024.2.3.25184
  3. Check if Foxit PDF Editor is installed
    On Windows, look in C:\Program Files\Foxit Software\ for Foxit PDF Editor. On macOS, check /Applications for Foxit PDF Editor.app. Search for 'Foxit PDF Editor' in the system if not found in default locations.
    Affected if Foxit PDF Editor is found on the system
  4. Determine Foxit PDF Editor version
    Open Foxit PDF Editor, then go to Help > About Foxit PDF Editor to display the exact version number. Alternatively, right-click the FoxitPDFEditor.exe file in the installation folder, select Properties, and check the Details tab for the Product Version.
    Affected if The installed version falls within any of these affected ranges: < 11.2.11.54113; >= 12.0.0.12394 and < 12.1.8.15703; >= 13.0.0.21632 and < 13.1.3.22478; >= 2023.1.0.15510 and < 2024.2.3.25184

You are affected if Foxit PDF Reader version is below 2024.2.3.25184, or Foxit PDF Editor version is below any of the specific version thresholds listed in the affected ranges.

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

Apply the vendor security update from Foxit when available. Until then, avoid opening untrusted PDF files and disable JavaScript execution in PDF Reader as a defense-in-depth measure.

Recommended fix High confidence

Upgrade to Foxit PDF Reader/Pdf Editor version 2024.2.3.25184 or later (or the equivalent fixed version for older major releases: 11.2.11.54113, 12.1.8.15703, or 13.1.3.22478)

  1. Identify whether Foxit PDF Reader or Foxit PDF Editor is installed, and determine the current version number
  2. Navigate to the official Foxit website (www.foxit.com) to download the latest version
  3. For Pdf Editor: upgrade to version 11.2.11.54113 or higher (if on 11.x), or 12.1.8.15703 or higher (if on 12.x), or 13.1.3.22478 or higher (if on 13.x), or 2024.2.3.25184 or higher (if on 2023/2024 versions)
  4. For Pdf Reader: upgrade to version 2024.2.3.25184 or higher
  5. Run the installer and follow the prompts to complete the update
  6. Restart the application and verify the version has been updated

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
  • Testing3.0 h
  • Review / QA1.0 h
10.0 hours of engineering $1,750
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,800.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-7723 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

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-7723 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