CVE-2025-66495
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 annotation handling of Foxit PDF Reader before 2025.2.1, 14.0.1, and 13.2.1 on Windows and MacOS. 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's annotation handling allows specially crafted JavaScript embedded in a PDF to access memory pointers that have already been freed. This can lead to arbitrary code execution when the attacker-controlled PDF is opened.
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<= 13.2.1.63315>= 14.0.0.33046, <= 14.0.1.69005>= 2023.1.0.15510, <= 2023.3.0.63083>= 2024.1.0.23997, <= 2024.4.1.66479>= 2025.1.0.27937, <= 2025.2.1.69005<= 2025.2.1.33197<= 2025.2.1.69005CVSS 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.
-
Identify Foxit PDF product installationOpen Windows Settings > Apps & Features or use PowerShell: Get-ItemProperty 'HKLM:\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\*' | Where-Object {$_.DisplayName -like '*Foxit*'} | Select-Object DisplayName, DisplayVersionAffected if Foxit PDF Reader or Foxit PDF Editor is installed
-
Determine exact version numberFor desktop app, click Help > About Foxit Reader/Editor. From command line (if installed): "C:\Program Files\Foxit Software\FoxitReader\FoxitReader.exe" -version (adjust path for Editor)Affected if Version cannot be determined or differs from installed product
-
Compare Reader version against affected rangesCompare your installed version to: <= 2025.2.1.33197 or <= 2025.2.1.69005. Note: Both Reader version constraints use <=, meaning all versions up to these are affected.Affected if Installed version is 2025.2.1.33197 or earlier, OR 2025.2.1.69005 or earlier (for builds with that version scheme)
-
Compare Editor version against affected rangesCompare against: <= 13.2.1.23955; 14.0.0.33046 to 14.0.1.33197; 2023.1.0.15510 to 2023.3.0.23028; 2024.1.0.23997 to 2024.4.1.27687; 2025.1.0.27937 to 2025.2.1.33197; also <= 13.2.1.63315; 14.0.0.33046 to 14.0.1.69005; 2023.1.0.15510 to 2023.3.0.63083; 2024.1.0.23997 to 2024.4.1.66479; 2025.1.0.27937 to 2025.2.1.69005Affected if Installed version falls within any of the listed ranges
-
Check if JavaScript is enabled in applicationOpen Foxit Reader/Editor, go to File > Preferences > JavaScript. Verify if Enable JavaScript is checked (typically enabled by default)Affected if JavaScript is enabled - the exploit requires JavaScript execution to trigger the use-after-free in annotation handling
You are affected if Foxit PDF Reader or Editor is installed and its version matches any of the affected ranges AND JavaScript is enabled in the application settings.
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 to version 2025.2.1, 14.0.1, 13.2.1 or later to patch the use-after-free vulnerability in annotation handling.
Pdf Editor: 13.2.2+, 14.0.2+, or 2024.4.2+/2025.x; Pdf Reader: 2025.2.2+ (or latest 2025.x)
- 1. Identify the installed Foxit product (Pdf Editor or Pdf Reader) and note the current version number
- 2. For Pdf Editor: Upgrade to version 13.2.1.23956 or later for the 13.x line, 14.0.1.33198 or later for the 14.x line, or the latest 2024.x/2025.x release
- 3. For Pdf Reader: Upgrade to version 2025.2.1.69006 or later (or the latest 2025.x release)
- 4. Download the updated version from the official Foxit website at www.foxit.com
- 5. Uninstall the current Foxit application
- 6. Install the updated version from the downloaded installer
- 7. Restart the application and verify the version number reflects the upgrade
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation3.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,272.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-66495 — 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-66495 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