dbcve.org
Pdf EditorApplication · Foxit

CVE-2025-66498

HIGH · 7.8 CVSS v3.1 Published 2025-12-19
Fix available
A fix is available. Upgrade to after 2025.2.1.33197 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 U3D 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

Foxit PDF Reader contains a memory corruption vulnerability in its 3D annotation parsing component. Insufficient bounds checking during U3D data processing allows malformed PRC content within PDF files to trigger out-of-bounds memory access, potentially enabling arbitrary code execution.

MitigationApply vendor-supplied patches from Foxit when available. Until then, mitigate by disabling 3D annotations in Foxit settings, enabling Protected View for untrusted files, and exercising caution with PDF sources.

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

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 the installed Foxit product and version
    Open Foxit and navigate to Help > About, or check the installed programs list in Windows Control Panel. Note whether you have Foxit PDF Reader or Foxit PDF Editor.
    Affected if The installed version falls within any of these vulnerable ranges: Foxit PDF Editor <= 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. Foxit PDF Reader versions <= 2025.2.1.3
  2. Verify if 3D annotation support is enabled in Foxit settings
    Open Foxit preferences or settings and look for options related to 3D annotations, U3D content, or multimedia content. Check whether the setting to enable or display 3D annotations is turned on.
    Affected if 3D annotation support is enabled, allowing Foxit to process U3D/PRC data within PDF files.
  3. Confirm Protected View or sandbox is not enforced for untrusted files
    Check Foxit security settings to see if Protected View is enabled for files from untrusted sources. This setting is typically found in File > Preferences > Security.
    Affected if Protected View is disabled or set to off, allowing untrusted PDF files to be opened with full functionality including 3D content processing.
  4. Check if the system routinely opens PDFs from untrusted or unknown sources
    Review your workflow for handling PDF files. Determine if you frequently open PDFs from email attachments, downloads, or other unverified sources that may contain 3D content.
    Affected if You regularly process PDF files from untrusted sources without sandbox protections, increasing the likelihood of encountering a malicious PRC/U3D payload.

You are affected if you have Foxit PDF Reader <= 2025.2.1.33197 or any vulnerable Foxit PDF Editor version listed, and 3D annotation processing is enabled while handling untrusted PDFs.

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.33197
Interim mitigation

Apply vendor-supplied patches from Foxit when available. Until then, mitigate by disabling 3D annotations in Foxit settings, enabling Protected View for untrusted files, and exercising caution with PDF sources.

Recommended fix Moderate confidence

Pdf Reader: 2025.2.2+ | Pdf Editor: 13.2.1.23956+, 14.0.1.33198+, 2023.3.0.23029+, or 2024.4.1.27688+ (depending on major version line)

  1. 1. Identify the exact Foxit product (Pdf Reader or Pdf Editor) and current installed version from Help > About Foxit PDF.
  2. 2. For Pdf Reader: Upgrade to version 2025.2.2 or later from https://www.foxit.com/pdf-reader/
  3. 3. For Pdf Editor: Upgrade to version 13.2.1.23956 or later for version 13.x; upgrade to version 14.0.1.33198 or later for version 14.x; upgrade to version 2023.3.0.23029 or later for 2023.x releases; upgrade to version 2024.4.1.27688 or later for 2024.x releases.
  4. 4. Download the appropriate installer from the official Foxit website.
  5. 5. Run the installer and follow the prompts to complete the upgrade.
  6. 6. Restart Foxit after the upgrade completes.
  7. 7. Verify the new version by checking Help > About Foxit PDF to confirm the vulnerability is remediated.
Caveat Standard minor version upgrades typically have minimal compatibility risks; review Foxit release notes for any plugin or feature changes

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

Fix this in Pdf Editor Scoped from the published advisory
  • Consultation3.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
8.0 hours of engineering $1,440
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,304.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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