dbcve.org
Pdf EditorApplication · Foxit

CVE-2025-55312

HIGH · 7.8 CVSS v3.1 Published 2025-12-11
Fix available
A fix is available. Upgrade to after 2025.1.0.66692 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
An issue was discovered in Foxit PDF and Editor for Windows before 13.2 and 2025 before 2025.2. When pages in a PDF are deleted via JavaScript, the application may fail to properly update internal states. Subsequent annotation management operations assume these states are valid, causing dereference of invalid or released memory. This can lead to memory corruption, application crashes, and potentially allow an attacker to execute arbitrary code.

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

This is a use-after-free vulnerability in Foxit PDF Editor for Windows. When JavaScript deletes PDF pages, the application fails to properly update internal state structures. Subsequent annotation management operations then dereference these invalid or already-released memory structures, causing corruption that can lead to code execution.

MitigationUpdate Foxit PDF Editor to version 13.2 or 2025.2 or later to obtain the vendor patch. Alternatively, consider disabling JavaScript execution in Foxit settings as a temporary workaround if updates are not immediately feasible.

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>= 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
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
    Open Control Panel > Programs and Features, or check Registry keys under HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall for entries containing 'Foxit PDF Editor' or 'Foxit PDF Reader'
    Affected if Either Foxit PDF Editor or Foxit PDF Reader is installed on the system
  2. Determine exact version number
    Right-click the Foxit application icon, select Properties, then look at the Version tab, or launch the application and go to Help > About to see the full version string including the build number
    Affected if The installed version cannot be determined or is not visible
  3. Compare against affected Editor versions
    Match the installed version string (e.g., 13.1.7.63027, 2023.1.0.55583, 2024.4.1.66479, 2025.1.0.66692) against these ranges: <= 13.1.7.63027; >= 2023.1.0.55583 AND <= 2023.3.0.63083; >= 2024.1.0.63682 AND <= 2024.4.1.66479; = 2025.1.0.66692; >= 2023.1.0.15510 AND <= 2023.3.0.23028; >= 2024.1.0.23997 AND <= 2024.4.1.27687; = 2025.1.0.27937
    Affected if The installed version falls within any of these ranges
  4. Compare against affected Reader versions
    Match the installed Foxit PDF Reader version against: <= 2025.1.0.66692 OR <= 2025.1.0.27937
    Affected if The installed Reader version is 2025.1.0.66692 or earlier, or 2025.1.0.27937 or earlier
  5. Check JavaScript execution status
    Launch Foxit, go to File > Preferences > JavaScript, or on newer versions navigate to File > Settings > JavaScript, and verify whether JavaScript is enabled or disabled
    Affected if JavaScript is enabled - the vulnerability requires JavaScript-triggered page deletion to trigger the use-after-free

You are affected if Foxit PDF Editor or Reader is installed with a version matching the affected ranges AND JavaScript execution is enabled in the application settings.

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 to obtain the vendor patch. Alternatively, consider disabling JavaScript execution in Foxit settings as a temporary workaround if updates are not immediately feasible.

Recommended fix High confidence

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

  1. 1. Open Foxit PDF Editor or PDF Reader application
  2. 2. Navigate to the Help menu or Account settings
  3. 3. Check the current version by selecting 'About Foxit PDF Editor' or 'About Foxit PDF Reader'
  4. 4. Download the fixed version from the official Foxit website (www.foxit.com) - ensure version 13.2 or later, or version 2025.2 or later
  5. 5. Close all Foxit applications
  6. 6. Run the installer for the new version
  7. 7. Follow the installation wizard prompts to complete the upgrade
  8. 8. After installation, verify the new version by checking 'About' to confirm the fix is applied
Caveat Standard minor version upgrade; no significant breaking changes expected for typical PDF operations

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
  • Implementation2.0 h
  • Testing1.0 h
  • Review / QA1.0 h
5.0 hours of engineering $890
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,424.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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