dbcve.org
Pdf EditorApplication · Foxit

CVE-2025-55308

MEDIUM · 6.7 CVSS v3.1 Published 2025-12-11
Fix available
A fix is available. Upgrade to after 2025.1.0.27937 or later.
See remediation →
67/100
Remediation priority · Elevated

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. A crafted PDF containing JavaScript that calls closeDoc() while internal objects are still in use can cause premature release of these objects. This use-after-free vulnerability may lead to memory corruption, potentially resulting in information disclosure when the PDF is opened.

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 Reader and Editor for Windows. A crafted PDF containing JavaScript calls the closeDoc() function while internal objects are still in use, causing those objects to be prematurely released from memory. When the application later attempts to access these freed objects, it leads to memory corruption that can result in information disclosure.

MitigationUpdate Foxit PDF Reader and Editor to version 13.2 or 2025.2 or later. As a temporary workaround, disable JavaScript execution in the Foxit application settings to prevent the malicious code from executing.

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

CVSS:3.1/AV:L/AC:H/PR:L/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
    Open Windows Control Panel > Programs and Features, or check the Start Menu shortcuts. Look for 'Foxit PDF Reader' or 'Foxit PDF Editor' to determine which product is installed.
    Affected if The system has Foxit PDF Reader or Foxit PDF Editor installed for Windows.
  2. Check the installed Foxit version number
    In Foxit, click Help > About Foxit PDF Reader (or Editor). Note the exact version number shown (for example, 13.1.7.23637 or 2025.1.0.27937).
    Affected if A version number is displayed, indicating Foxit software is present.
  3. Compare your version to affected ranges
    Match your installed version against these affected ranges: Editor versions <= 13.1.7.23637; >= 2023.1.0.15510 through <= 2023.3.0.23028; >= 2024.1.0.23997 through <= 2024.4.1.27687; exactly 2025.1.0.27937. Reader versions <= 2025.1.0.27937.
    Affected if Your installed version falls within any of these affected ranges.
  4. Verify if JavaScript execution is enabled
    In Foxit, go to File > Preferences > JavaScript. Check if 'Enable JavaScript' is checked/enabled.
    Affected if JavaScript is enabled. This is required for the crafted PDF to trigger the vulnerability.

You are affected if you have Foxit PDF Reader or Editor installed with a version matching the affected ranges AND JavaScript 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.27937
Interim mitigation

Update Foxit PDF Reader and Editor to version 13.2 or 2025.2 or later. As a temporary workaround, disable JavaScript execution in the Foxit application settings to prevent the malicious code from executing.

Recommended fix High confidence

Foxit PDF Editor 13.2 or later / Foxit PDF Reader 2025.2 or later

  1. Open Foxit PDF Editor or Reader and navigate to Help > Check for Updates to see current version
  2. Download the latest version of Foxit PDF Editor (13.2 or later) or Foxit PDF Reader (2025.2 or later) from the official Foxit website at www.foxit.com
  3. Close any open instances of Foxit PDF Editor or Reader
  4. Run the downloaded installer and follow the prompts to complete the upgrade
  5. After installation, verify the version by checking Help > About to confirm the fix is applied
Caveat Verify compatibility with any third-party PDF plugins or workflows after upgrading

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
  • Implementation1.0 h
  • Testing2.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,060
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,696.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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