dbcve.org
Pdf EditorApplication · Foxit

CVE-2025-66497

HIGH · 7.8 CVSS v3.1 Published 2025-12-19
Fix available
A fix is available. Upgrade to after 2025.2.1.69005 or later.
See remediation →
81/100
Remediation priority · High
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
A memory corruption vulnerability exists in the 3D annotation handling of Foxit PDF Reader due to insufficient bounds checking when parsing PRC data. When opening a PDF file containing malformed or specially crafted PRC content, out-of-bounds memory access may occur, resulting in memory corruption.

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 memory corruption vulnerability exists in Foxit PDF Reader's 3D annotation handling due to insufficient bounds checking when parsing PRC (Product Representation Compact) data. When a user opens a PDF containing malformed or specially crafted PRC content within 3D annotations, the insufficient bounds validation allows out-of-bounds memory access, leading to memory corruption that could be exploited for arbitrary code execution.

MitigationUsers should avoid opening PDF files from untrusted sources until an official patch is released by Foxit. Organizations should monitor for Foxit security updates and apply them promptly once available.

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:<= 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
Pdf ReaderApplication
Affected:<= 2025.2.1.33197<= 2025.2.1.69005

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

Work through these to decide whether this CVE applies to you.

  1. Identify installed Foxit product
    Check for Foxit PDF Reader or Foxit PDF Editor in installed programs (Control Panel > Programs and Features, or check C:\Program Files\Foxit Software or C:\Program Files (x86)\Foxit Software directories)
    Affected if Either Foxit PDF Reader or Foxit PDF Editor is installed on the system
  2. Determine installed version of Foxit PDF Reader
    Open Foxit Reader, click Help > About Foxit Reader, or right-click the application in Programs and Features and select Properties to view the version number
    Affected if Version is <= 2025.2.1.33197 or <= 2025.2.1.69005 (the exact version number shown determines which range applies)
  3. Determine installed version of Foxit PDF Editor
    Open Foxit PDF Editor, click Help > About Foxit PDF Editor, or right-click the application in Programs and Features and select Properties to view the version number
    Affected if Version falls within any of these ranges: <= 13.2.1.23955; >= 14.0.0.33046 and <= 14.0.1.33197; >= 2023.1.0.15510 and <= 2023.3.0.23028; >= 2024.1.0.23997 and <= 2024.4.1.27687; >= 2025.1.0.27937 and <= 2025.2.1.33197; <= 13.2.1.63315; >= 14.0.0.33046 and <= 14.0.1.69005; >= 2023.1.0.15510 and <= 20
  4. Assess exposure to 3D PDF content
    Determine if the environment commonly opens PDF files that may contain 3D annotations (common in technical, engineering, or CAD-related documents). This is a passive check - the vulnerability triggers simply by opening a malformed PDF, no special configuration is required.
    Affected if Users routinely open PDF files from varied or untrusted sources, increasing likelihood of encountering a specially crafted PDF with malformed PRC 3D content

The system is affected if Foxit PDF Reader or Foxit PDF Editor is installed and the installed version matches any of the affected version ranges listed for this CVE.

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 a release after 2025.2.1.69005
Interim mitigation

Users should avoid opening PDF files from untrusted sources until an official patch is released by Foxit. Organizations should monitor for Foxit security updates and apply them promptly once available.

Recommended fix Moderate confidence

Latest Foxit PDF Reader/PDF Editor version (contact Foxit support for specific patch release numbers)

  1. 1. Navigate to the Foxit software and access the Help menu
  2. 2. Select 'Check for Updates' or visit the official Foxit website at www.foxit.com to download the latest version
  3. 3. Download and install the latest version of Foxit PDF Reader or PDF Editor
  4. 4. Restart the application after installation
  5. 5. Verify the version number matches a release higher than the affected versions listed (above 13.2.1.23955, above 14.0.1.33197, above 2023.3.0.23028, above 2024.4.1.27687 for Editor; above 2025.2.1.69005 for Reader)
Caveat Review release notes for any compatibility or feature changes between your current and the new version

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Pdf Editor Scoped from the published advisory
  • Consultation6.0 h
  • Implementation12.0 h
  • Testing6.0 h
  • Review / QA3.0 h
27.0 hours of engineering $4,800
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $7,680.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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