CVE-2024-7725
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 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-23928.
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 confidenceFoxit PDF Reader contains a use-after-free vulnerability in its AcroForm handling functionality. The vulnerability stems from the application failing to validate the existence of an object before performing operations on it, allowing an attacker to manipulate memory and achieve arbitrary code execution in the context of the current 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.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< 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
- 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 checksWork through these to decide whether this CVE applies to you.
-
Identify the Foxit product installedOpen Foxit PDF Reader or PDF Editor. Go to Help > About Foxit PDF Reader (or About Foxit PDF Editor) to confirm whether you have the Reader or Editor variant installed.Affected if The product is Foxit PDF Reader or Foxit PDF Editor.
-
Locate the installed version numberIn the About dialog, note the exact version number displayed (for example, it may show a build number like 11.2.11.54113 or 2024.2.3.25184).Affected if A version number is visible in the About dialog.
-
Compare your version to affected rangesFor Foxit PDF Editor: check if version is < 11.2.11.54113 OR (>= 12.0.0.12394 AND < 12.1.8.15703) OR (>= 13.0.0.21632 AND < 13.1.3.22478) OR (>= 2023.1.0.15510 AND < 2024.2.3.25184). For Foxit PDF Reader: check if version is < 2024.2.3.25184.Affected if Your installed version falls within any of the affected ranges listed.
-
Assess AcroForm exposureAcroForm is a standard PDF feature for interactive forms. If you regularly open PDF files that contain fillable form fields, your installation is processing AcroForm content. The vulnerability triggers when opening a specially crafted malicious PDF with AcroForm objects.Affected if You open PDF files with AcroForm content from untrusted sources.
You are affected if you have an unpatched version of Foxit PDF Reader or Foxit PDF Editor and you open PDF files (especially from untrusted sources) that contain 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 · scoped11.2.11.5411312.1.8.1570313.1.3.22478
Apply the vendor patch from Foxit when available. Until then, enforce user awareness to avoid opening untrusted PDF files and disable automatic opening of PDF attachments from unknown sources.
Foxit Pdf Reader: 2024.2.3.25184 or later; Foxit Pdf Editor: 11.2.11.54113 (11.x), 12.1.8.15703 (12.x), 13.1.3.22478 (13.x), or 2024.2.3.25184 (2023.x/2024.x)
- 1. Identify the installed Foxit product (Pdf Editor or Pdf Reader) and note the current version number from the application's Help > About menu
- 2. For Foxit Pdf Reader: Navigate to the official Foxit website downloads page (www.foxit.com) and download version 2024.2.3.25184 or later
- 3. For Foxit Pdf Editor: Determine which version branch is currently installed (11.x, 12.x, 13.x, or 2023.x) and download the corresponding minimum fixed version: 11.2.11.54113, 12.1.8.15703, 13.1.3.22478, or 2024.2.3.25184
- 4. Close all Foxit applications and any PDF files currently open
- 5. Run the downloaded installer with administrator privileges
- 6. Follow the installation wizard prompts to complete the upgrade
- 7. After installation, verify the new version by checking Help > About to confirm the version meets or exceeds the fixed release for your branch
- 8. Test that PDF files with AcroForms open and function correctly
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation4.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 $2,560.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-7725 — 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-7725 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