dbcve.org
Pdf EditorApplication · Foxit

CVE-2025-9325

MEDIUM · 5.5 CVSS v3.1 Published 2025-09-02
Fix available
A fix is available. Upgrade to 2025.1.0.27937 or later.
See remediation →
58/100
Remediation priority · Elevated
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 Reader PRC File Parsing Out-Of-Bounds Read Information Disclosure Vulnerability. This vulnerability allows remote attackers to disclose sensitive information on affected installations of Foxit PDF Reader. User interaction is required to exploit this vulnerability in that the target must visit a malicious page or open a malicious file. The specific flaw exists within the parsing of PRC files. The issue results from the lack of proper validation of user-supplied data, which can result in a read past the end of an allocated object. An attacker can leverage this in conjunction with other vulnerabilities to execute arbitrary code in the context of the current process. Was ZDI-CAN-26785.

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 · moderate confidence

An out-of-bounds read vulnerability exists in Foxit PDF Reader's PRC file parser due to insufficient validation of user-supplied data. The lack of proper bounds checking during PRC file parsing allows reading past the end of an allocated object, resulting in information disclosure.

MitigationApply vendor patches when available; avoid opening untrusted PRC files or visiting malicious webpages until the vulnerability is remediated.

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<= 13.1.7.63027>= 2023.1.0.55583, <= 2023.3.0.63083>= 2024.1.0.63682, <= 2024.4.1.66479= 2025.1.0.66692
Pdf ReaderApplication
Affected:< 2025.1.0.27937<= 2025.1.0.66692

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
None
Availability
None

CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:N/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. Confirm Foxit PDF product is installed
    Check for Foxit PDF Reader or Foxit PDF Editor installation by looking in 'C:\Program Files\Foxit Software\' or 'C:\Program Files (x86)\Foxit Software\' directories, or by checking Windows Registry under HKLM\SOFTWARE\Foxit Software or HKLM\SOFTWARE\WOW6432Node\Foxit Software
    Affected if Foxit PDF Reader or Foxit PDF Editor is found on the system
  2. Identify the installed version
    Right-click the Foxit PDF executable (e.g., FoxitReader.exe or FoxitPDFEditor.exe), select Properties, and view the Details tab for the Product version; alternatively, check the version value in the Windows Registry under the Foxit installation key
    Affected if Version cannot be determined or does not match any Foxit version format
  3. Compare against affected Foxit PDF Reader versions
    Compare your installed version number to the affected ranges: < 2025.1.0.27937 OR <= 2025.1.0.66692. Note that 2025.1.0.27937 itself is not listed as affected for Reader, so versions strictly less than 2025.1.0.27937 are affected, and versions <= 2025.1.0.66692 are also affected.
    Affected if Installed version is less than 2025.1.0.27937 OR is between 2025.1.0.27938 and 2025.1.0.66692 (inclusive)
  4. Compare against affected Foxit PDF Editor versions
    Compare your installed version to the multiple affected ranges: <= 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; <= 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
    Affected if Installed version matches any of the listed affected ranges for Foxit PDF Editor

The system is affected if Foxit PDF Reader version is less than 2025.1.0.27937 or is between 2025.1.0.27938 and 2025.1.0.66692 inclusive, OR if Foxit PDF Editor version falls within any of the multiple affected ranges provided.

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 2025.1.0.27937 or later
Fixed in 2025.1.0.27937
Interim mitigation

Apply vendor patches when available; avoid opening untrusted PRC files or visiting malicious webpages until the vulnerability is remediated.

Recommended fix High confidence

Upgrade to the latest Foxit PDF Reader/PDF Editor version (available at www.foxit.com) which addresses the PRC file parsing out-of-bounds read vulnerability.

  1. 1. Open Foxit PDF Reader or PDF Editor.
  2. 2. Navigate to Help > Check for Updates or About Foxit to identify your current version.
  3. 3. If an update is available, download and install the latest version from the official Foxit website at www.foxit.com.
  4. 4. Alternatively, visit www.foxit.com and download the most recent release of Foxit PDF Reader or PDF Editor.
  5. 5. Restart the application after installation.
  6. 6. Verify the installed version matches or exceeds the fixed release.
Caveat Standard upgrade risk - review release notes for any significant feature changes before deploying in production environments.

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
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,930
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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