dbcve.org
Pdf EditorApplication · Foxit

CVE-2025-59802

HIGH · 7.5 CVSS v3.1 Published 2025-12-11
Fix available
A fix is available. Upgrade to after 2025.2.0.68868 or later.
See remediation →
84/100
Remediation priority · High
Remotely reachable No privileges Zero-click

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
Foxit PDF Editor and Reader before 2025.2.1 allow signature spoofing via OCG. When Optional Content Groups (OCG) are supported, the state property of an OCG is runtime-only and not included in the digital signature computation buffer. An attacker can leverage JavaScript or PDF triggers to dynamically change the visibility of OCG content after signing (Post-Sign), allowing the visual content of a signed PDF to be modified without invalidating the signature. This may result in a mismatch between the signed content and what the signer or verifier sees, undermining the trustworthiness of the digital signature. The fixed versions are 2025.2.1, 14.0.1, and 13.2.1.

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 Editor and Reader before 2025.2.1 contain a signature spoofing vulnerability in Optional Content Groups (OCG). Since OCG visibility states are runtime-only and excluded from digital signature computation buffers, attackers can use JavaScript or PDF triggers to dynamically change OCG visibility after signing, allowing visual content modification without invalidating the digital signature.

MitigationUpgrade Foxit PDF Editor/Reader to version 2025.2.1, 14.0.1, or 13.2.1. Additionally, verify PDF signatures with OCG content rendering disabled to detect any visibility-based tampering.

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.0.63256>= 2023.1.0.55583, <= 2023.3.0.63083>= 2024.1.0.63682, <= 2024.4.1.66479= 14.0.0.68868= 2025.1.0.66692= 2025.2.0.68868<= 13.2.0.23874>= 2023.1.0.15510, <= 2023.3.0.23028>= 2024.1.0.23997, <= 2024.4.1.27687= 14.0.0.33046= 2025.1.0.27937= 2025.2.0.33046
Pdf ReaderApplication
Affected:<= 2025.2.0.68868<= 2025.2.0.33046

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
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
High
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N

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. Determine Foxit PDF Editor or Reader version
    In Foxit, go to Help > About Foxit PDF Editor (or Reader). Note the full version number including the build number.
    Affected if The installed version falls within any of these ranges: <=13.2.0.63256; >=2023.1.0.55583 to <=2023.3.0.63083; >=2024.1.0.63682 to <=2024.4.1.66479; =14.0.0.68868; =2025.1.0.66692; =2025.2.0.68868 (new build) OR <=13.2.0.23874; >=2023.1.0.15510 to <=2023.3.0.23028; >=2024.1.0.23997 to <=2024.4.1.2768
  2. Identify if the PDF contains Optional Content Groups (OCG)
    Open the PDF in a text editor and search for the strings '/OC' or '/OCProperties', or use a PDF analysis tool to enumerate OCG objects within the document structure.
    Affected if The PDF contains OCG entries (OCG dictionary objects or OCProperties) indicating optional content groups are present in the document.
  3. Check if the PDF has a digital signature
    In Foxit, look for the signature icon in the navigation pane or use the Document > Signatures menu. Alternatively, search for '/Sig' or '/ByteRange' in the PDF source.
    Affected if The PDF contains one or more digital signature fields (/Sig) with defined signature dictionaries.
  4. Verify if JavaScript or PDF triggers can execute
    In Foxit, check Preferences > JavaScript (or Security > Scripting) to see if JavaScript execution is enabled. For the specific PDF, examine embedded JavaScript code in the document-level scripts or in OCG action triggers.
    Affected if JavaScript execution is enabled in Foxit preferences AND the PDF contains JavaScript code tied to OCG visibility changes (such as 'OCG' or 'setOCGState' actions).
  5. Inspect OCG visibility state changes in signed documents
    Open the signed PDF and toggle OCG layer visibility on and off using the Layers panel. Then re-validate the digital signature to see if it still shows as valid despite the visual change.
    Affected if Changing OCG layer visibility after signing does not invalidate the digital signature, indicating the signature is vulnerable to OCG-based spoofing.

A user is affected if they are running an affected Foxit version (pre-2025.2.1/14.0.1/13.2.1) AND viewing PDFs that contain both OCG content and digital signatures, with JavaScript or trigger-based OCG manipulation possible.

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

Upgrade Foxit PDF Editor/Reader to version 2025.2.1, 14.0.1, or 13.2.1. Additionally, verify PDF signatures with OCG content rendering disabled to detect any visibility-based tampering.

Recommended fix High confidence

Upgrade to Foxit PDF Editor/Reader 2025.2.1, 14.0.1, or 13.2.1 depending on your current version line

  1. 1. Identify the currently installed Foxit PDF Editor or Reader version by opening the application and navigating to Help > About
  2. 2. Determine which version line you are on (13.x, 14.x, or the 2023-2025 annual release cycle)
  3. 3. Download the appropriate fixed version from the official Foxit website: 13.2.1 for version 13.x, 14.0.1 for version 14.x, or 2025.2.1 for the 2023-2025 releases
  4. 4. Uninstall the current Foxit application via Windows Control Panel > Programs and Features
  5. 5. Run the installer for the new fixed version
  6. 6. After installation, verify the version by checking Help > About to confirm the fix is applied
  7. 7. Re-validate any previously signed PDF documents that may have been affected by this vulnerability

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

Fix this in Pdf Editor Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing2.0 h
  • Review / QA1.0 h
9.0 hours of engineering $1,600
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,560.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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