CVE-2025-66493
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 · uneditedA use-after-free vulnerability exists in the AcroForm handling of Foxit PDF Reader and Foxit PDF Editor before 2025.2.1,14.0.1 and 13.2.1 on Windows . When opening a PDF containing specially crafted JavaScript, a pointer to memory that has already been freed may be accessed or dereferenced, potentially allowing a remote attacker to execute arbitrary code.
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 confidenceA use-after-free vulnerability in Foxit PDF Reader and Editor's AcroForm handling allows specially crafted JavaScript within a PDF to access memory that has already been freed. This can lead to arbitrary code execution when a user opens a malicious PDF file.
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<= 13.2.1.23955>= 14.0.0.33046, <= 14.0.1.33197>= 2023.1.0.15510, <= 2023.3.0.23028>= 2024.1.0.23997, <= 2024.4.1.27687>= 2025.1.0.27937, <= 2025.2.1.33197<= 2025.2.1.33197CVSS 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.1/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 software is installedLook for Foxit PDF Reader or Foxit PDF Editor in the program list (Control Panel > Programs and Features), or check common installation paths such as C:\Program Files\Foxit Software or C:\Program Files (x86)\Foxit SoftwareAffected if Foxit PDF Reader or Foxit PDF Editor is installed on the system
-
Determine the installed Foxit versionRight-click the Foxit executable (e.g., FoxitReader.exe or FoxitPDFEditor.exe), select Properties, and view the Details tab for the Product Version. Alternatively, open Foxit, go to Help > About to see the version numberAffected if The installed version cannot be determined or the software is present but version is unknown
-
Compare installed version to affected ranges for Foxit PDF EditorFor Foxit PDF Editor, note that versions <= 13.2.1.23955, 14.0.0.33046 through 14.0.1.33197, 2023.1.0.15510 through 2023.3.0.23028, 2024.1.0.23997 through 2024.4.1.27687, and 2025.1.0.27937 through 2025.2.1.33197 are vulnerable. Match your installed version against these rangesAffected if The installed Foxit PDF Editor version falls within any of the affected ranges listed
-
Compare installed version to affected ranges for Foxit PDF ReaderFor Foxit PDF Reader, note that versions <= 2025.2.1.33197 are vulnerable. If your installed version is 2025.2.1.33197 or lower, it is affectedAffected if The installed Foxit PDF Reader version is 2025.2.1.33197 or lower
If Foxit PDF Reader or Foxit PDF Editor is installed and the installed version falls within the affected ranges listed for the respective product, the environment is vulnerable to this CVE.
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 · scopedUpdate Foxit PDF Reader and Foxit PDF Editor to versions 2025.2.1, 14.0.1, or 13.2.1 or later to remediate this vulnerability.
Foxit PDF Reader: 2025.2.1 or later; Foxit PDF Editor: 13.2.1+, 14.0.1+, or latest 2023/2024 release
- 1. Identify the currently installed Foxit PDF Reader or Foxit PDF Editor version by opening the application and navigating to Help > About (or similar)
- 2. For Foxit PDF Reader users: Upgrade to version 2025.2.1 or later from the official Foxit website at www.foxit.com
- 3. For Foxit PDF Editor version 13.x users: Upgrade to version 13.2.1 or later
- 4. For Foxit PDF Editor version 14.x users: Upgrade to version 14.0.1 or later
- 5. For Foxit PDF Editor version 2023.x users: Upgrade to version 2023.3.0 or later (or the latest 2023 release)
- 6. For Foxit PDF Editor version 2024.x users: Upgrade to version 2024.4.1 or later (or the latest 2024 release)
- 7. After upgrading, verify the new version by checking Help > About
- 8. Exercise caution when opening PDF files from untrusted sources, as the vulnerability is triggered by specially crafted JavaScript within PDF files
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation2.0 h
- Testing1.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,744.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-66493 — 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-2025-66493 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