dbcve.org
Pdf EditorApplication · Foxit

CVE-2025-55311

MEDIUM · 6.5 CVSS v3.1 Published 2025-12-11
Fix available
A fix is available. Upgrade to after 2025.1.0.66692 or later.
See remediation →
72/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
An issue was discovered in Foxit PDF and Editor for Windows and macOS before 13.2 and 2025 before 2025.2. A crafted PDF can use JavaScript to alter annotation content and subsequently clear the file's modification status via JavaScript interfaces. This circumvents digital signature verification by hiding document modifications, allowing an attacker to mislead users about the document's integrity and compromise the trustworthiness of signed PDFs.

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 for Windows and macOS versions before 13.2 and 2025.2 contain a vulnerability where malicious JavaScript embedded in a crafted PDF can modify annotation content and then clear the document's modification status through JavaScript interfaces. This allows attackers to bypass digital signature verification by making signed documents appear unmodified despite having altered content.

MitigationUpdate Foxit PDF Editor to version 13.2 or 2025.2 or later. Organizations should also consider re-validating previously signed PDFs for integrity.

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.1.7.63027>= 2023.1.0.55583, <= 2023.3.0.63083>= 2024.1.0.63682, <= 2024.4.1.66479= 2025.1.0.66692<= 13.1.7.23637>= 2023.1.0.15510, <= 2023.3.0.23028>= 2024.1.0.23997, <= 2024.4.1.27687= 2025.1.0.27937
Pdf ReaderApplication
Affected:<= 2025.1.0.66692<= 2025.1.0.27937

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

CVSS:3.1/AV:N/AC:L/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. Check if Foxit PDF software is installed
    On Windows, open Programs and Features or check C:\Program Files\Foxit Software\ for Foxit directories. On macOS, check /Applications for Foxit PDF Editor or Foxit PDF Reader apps.
    Affected if Foxit PDF Editor or Foxit PDF Reader is present on the system
  2. Locate the installed version number
    On Windows, right-click the Foxit icon, select Properties, and check the Details tab for version information. On macOS, right-click the Foxit app in Applications, select Get Info, and view the Version field.
    Affected if Version number cannot be determined or is within the affected ranges
  3. Compare your Editor version to affected Windows builds
    For Foxit PDF Editor on Windows: version 13.x builds <= 13.1.7.63027 are affected. Versions 2023.1.0.55583 through 2023.3.0.63083, 2024.1.0.63682 through 2024.4.1.66479, and build 2025.1.0.66692 are affected.
    Affected if Installed version matches any of these vulnerable Windows builds
  4. Compare your Editor version to affected macOS builds
    For Foxit PDF Editor on macOS: versions 2023.1.0.15510 through 2023.3.0.23028, 2024.1.0.23997 through 2024.4.1.27687, and build 2025.1.0.27937 are affected. Also version 13.x builds <= 13.1.7.23637 are affected.
    Affected if Installed version matches any of these vulnerable macOS builds
  5. Compare your Reader version to affected builds
    For Foxit PDF Reader: Windows build <= 2025.1.0.66692 and macOS build <= 2025.1.0.27937 are affected.
    Affected if Installed Reader version is at or below these build numbers

You are affected if Foxit PDF Editor or Reader is installed and the version/build number falls within any of the listed vulnerable ranges for your platform.

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

Update Foxit PDF Editor to version 13.2 or 2025.2 or later. Organizations should also consider re-validating previously signed PDFs for integrity.

Recommended fix High confidence

Foxit PDF Editor 13.2+ or 2025.2+; Foxit PDF Reader 2025.2+

  1. 1. Identify your current version of Foxit PDF Editor or Foxit PDF Reader from the Help > About menu
  2. 2. Download the fixed version from the official Foxit website (www.foxit.com) - ensure version 13.2 or higher for the 13.x line, or version 2025.2 or higher for the yearly release line
  3. 3. Close all instances of Foxit PDF applications
  4. 4. Uninstall the current version of Foxit PDF Editor or Reader from your system
  5. 5. Install the newly downloaded fixed version (13.2+/2025.2+)
  6. 6. Restart the application and verify the version in Help > About matches the fixed release

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

Fix this in Pdf Editor Scoped from the published advisory
  • Consultation1.0 h
  • Implementation1.0 h
  • Testing2.0 h
  • Review / QA1.0 h
5.0 hours of engineering $860
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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