dbcve.org
Pdf EditorApplication · Foxit

CVE-2025-59803

MEDIUM · 5.3 CVSS v3.1 Published 2025-12-11
Fix available
A fix is available. Upgrade to after 2025.2.0.68868 or later.
See remediation →
60/100
Remediation priority · Elevated
Remotely reachable 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
Foxit PDF Editor and Reader before 2025.2.1 allow signature spoofing via triggers. An attacker can embed triggers (e.g., JavaScript) in a PDF document that execute during the signing process. When a signer reviews the document, the content appears normal. However, once the signature is applied, the triggers modify content on other pages or optional content layers without explicit warning. This can cause the signed PDF to differ from what the signer saw, 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 version 2025.2.1 (and affected 14.0.1/13.2.1) allows signature spoofing through embedded triggers (JavaScript) in PDF documents. These triggers execute during the signing process, making content appear normal to the signer, but then modify other pages or optional content layers after the signature is applied, causing the signed document to differ from what was originally reviewed.

MitigationUpgrade Foxit PDF Editor/Reader to version 2025.2.1, 14.0.1, or 13.2.1 to patch the vulnerability and prevent signature spoofing attacks.

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

CVSS:3.1/AV:N/AC:H/PR:N/UI:R/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. Identify installed Foxit product
    Open the application and go to Help > About Foxit PDF Editor/Reader to view the exact version number, or check Add/Remove Programs (Windows) / Applications folder (Mac) for the installed version
    Affected if Foxit PDF Editor or Reader is installed on the system
  2. Confirm version number
    Note the full version string shown in the About dialog (format varies: either x.x.x.xxxx or YEAR.Version.xxxx)
    Affected if The displayed version matches any of the affected version ranges listed in the CVE
  3. Compare against affected Editor versions (13.x)
    If version starts with 13.2.0, check if it is <= 13.2.0.63256 (newer format) or <= 13.2.0.23874 (older format)
    Affected if Version falls within 13.2.0.63256 or lower, or 13.2.0.23874 or lower
  4. Compare against affected Editor versions (2023-2025)
    For 2023.x versions, check if between 2023.1.0.55583 and 2023.3.0.63083 (newer) or between 2023.1.0.15510 and 2023.3.0.23028 (older). For 2024.x, check between 2024.1.0.63682 and 2024.4.1.66479 (newer) or between 2024.1.0.23997 and 2024.4.1.27687 (older). For specific 14.x and 2025.x versions, check if equal to listed versions
    Affected if Version falls within or matches any of these specific ranges: 2023.1.0.55583-2023.3.0.63083, 2023.1.0.15510-2023.3.0.23028, 2024.1.0.63682-2024.4.1.66479, 2024.1.0.23997-2024.4.1.27687, 14.0.0.68868, 14.0.0.33046, 2025.1.0.66692, 2025.1.0.27937, 2025.2.0.68868, or 2025.2.0.33046
  5. Compare against affected Reader versions
    If using Foxit PDF Reader, check if version is <= 2025.2.0.68868 (newer format) or <= 2025.2.0.33046 (older format)
    Affected if Reader version is 2025.2.0.68868 or lower, or 2025.2.0.33046 or lower

The environment is affected if Foxit PDF Editor or Reader version matches any of the specific version ranges or exact versions listed in the CVE, and the user works with digitally signed PDF documents.

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 to patch the vulnerability and prevent signature spoofing attacks.

Recommended fix High confidence

2025.2.1 (for versions 2023.x/2024.x/2025.x), 14.0.1 (for version 14.x), or 13.2.1 (for version 13.x)

  1. 1. Identify the currently installed Foxit PDF Editor or Reader version from the application's Help > About menu
  2. 2. Determine which upgrade path applies based on current version: if using version 13.x, upgrade to 13.2.1; if using version 14.x, upgrade to 14.0.1; if using version 2023.x, 2024.x, or 2025.x, upgrade to 2025.2.1
  3. 3. Download the appropriate fixed version from the official Foxit website (www.foxit.com)
  4. 4. Close all instances of the Foxit application
  5. 5. Uninstall the current version using Windows Settings > Apps or the application's uninstaller
  6. 6. Install the downloaded fixed version by running the installer and following the prompts
  7. 7. Launch the application and verify the version matches the expected fixed release in Help > About
  8. 8. Test that PDF signing functionality works correctly with the patched version
Caveat Minimal risk - this is a security patch upgrade with no major feature changes expected; always backup custom settings if applicable

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
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
16.0 hours of engineering $2,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 $4,480.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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