dbcve.org
Pdf EditorApplication · Foxit

CVE-2025-55310

HIGH · 7.3 CVSS v3.1 Published 2025-12-11
Fix available
A fix is available. Upgrade to after 2025.1.0.66692 or later.
See remediation →
73/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 and macOS before 13.2 and 2025 before 2025.2. An attacker able to alter or replace the static HTML files used by the StartPage feature can cause the application to load malicious or compromised content upon startup. This may result in information disclosure, unauthorized data access, or other security impacts.

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's StartPage feature loads static HTML files on application startup. An attacker with file system access can modify these HTML files to inject malicious content that loads when the application starts, leading to information disclosure or unauthorized data access.

MitigationUpdate Foxit PDF Editor to version 13.2 or 2025.2 and later. Additionally, review and restrict file system permissions on the StartPage HTML files to prevent unauthorized modification.

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

CVSS:3.1/AV:L/AC:L/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. Confirm Foxit PDF Editor or Reader is installed
    Check the installed programs list in Control Panel > Programs and Features, or use the Add or Remove Programs list. Look for Foxit PDF Editor or Foxit PDF Reader.
    Affected if Either Foxit PDF Editor or Foxit PDF Reader is present on the system.
  2. Determine the installed version
    Open Foxit, then go to Help > About to view the exact version number and build. Alternatively, right-click the Foxit application shortcut and select Properties to see the version information.
    Affected if The version falls within any of these affected 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; <= 13.1.7.23637; >= 2023.1.0.15510 and <= 2023.3.0.23028; >= 2024.1.0.23997 and <= 2024.4.1.27687; = 2025.1.0.27937 (for Reader:
  3. Locate the StartPage HTML files
    Search the Foxit installation directory for HTML files related to StartPage functionality. Common file names may include startpage.html, welcome.html, or similar files in the folders /config, /resources, or /ui. Consult Foxit documentation if available for the exact file names and locations.
    Affected if StartPage HTML files exist in the Foxit installation directory.
  4. Inspect StartPage HTML files for injected content
    Open the StartPage HTML files in a text editor and review the script tags, iframe elements, or external resource references. Look for unfamiliar domains, base64-encoded payloads, or code that was not authored by Foxit.
    Affected if The HTML files contain suspicious script tags, external resource loads, or content that does not match the expected Foxit startup page.
  5. Check file system permissions on StartPage HTML files
    Right-click each StartPage HTML file, go to Properties > Security, and review which users or groups have Write or Modify permissions. Also check the file ownership.
    Affected if Users without administrative privileges or unauthorized accounts have Write or Modify permissions to the StartPage HTML files.

A user is affected if Foxit PDF Editor or Reader is installed with a version matching the affected ranges AND the StartPage HTML files can be modified by an attacker to inject malicious content.

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 and later. Additionally, review and restrict file system permissions on the StartPage HTML files to prevent unauthorized modification.

Recommended fix High confidence

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

  1. 1. Determine which Foxit product is installed (PDF Editor or PDF Reader) and the current version number
  2. 2. For Foxit PDF Editor: Upgrade to version 13.2 or later (or a newer 2025.x version beyond 2025.1.0.66692)
  3. 3. For Foxit PDF Reader: Upgrade to version 2025.2 or later
  4. 4. Download the latest version from the official Foxit website at www.foxit.com
  5. 5. Run the installer and follow the prompts to complete the upgrade
  6. 6. Verify the installed version matches the fixed release 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
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
7.0 hours of engineering $1,240
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,984.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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