CVE-2025-9328
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 · uneditedFoxit PDF Reader PRC File Parsing Out-Of-Bounds Read Remote Code Execution Vulnerability. This vulnerability allows remote attackers to execute arbitrary code 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 buffer. An attacker can leverage this vulnerability to execute code in the context of the current process. Was ZDI-CAN-26773.
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 confidenceFoxit PDF Reader contains an out-of-bounds read vulnerability in its PRC file parser due to insufficient validation of user-supplied data. The flaw allows reading past the end of an allocated buffer during PRC file parsing, which can be leveraged to achieve remote code execution in the context of the current user process.
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<= 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< 2025.1.0.27937<= 2025.1.0.66692CVSS 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.0/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 checksWork through these to decide whether this CVE applies to you.
-
Identify Foxit PDF product and versionOpen Foxit PDF Reader or Foxit PDF Editor, then navigate to Help > About (or similar menu option) to view the exact version number displayed in the About dialog. Alternatively, check the installed program's version property in Windows Programs and Features.Affected if The installed version falls within the affected ranges: for Reader, versions < 2025.1.0.27937 or <= 2025.1.0.66692; for Editor, versions <= 13.1.7.23637, >= 2023.1.0.15510 to <= 2023.3.0.23028, >= 2024.1.0.23997 to <= 2024.4.1.27687, or = 2025.1.0.27937, or versions <= 13.1.7.63027, >= 2023.1.0.5558
-
Confirm PRC file support is presentCheck if Foxit has native PRC (PrcFileS.ax or similar plugin module) support by examining the Foxit plugin folder (commonly in the installation directory under plugins or UPF folder). Look for a PRC-related plugin component or check if the application can open .prc file extensions.Affected if The PRC parsing module exists and is accessible within the Foxit installation, meaning the application can process PRC files.
-
Locate recent PRC files in the environmentSearch for .prc files on local systems using file explorer search or command: dir /s /b C:\*.prc (adjust drive letter as needed). Review recent downloads folder or commonly accessed document directories.Affected if PRC files exist in accessible locations and the Foxit version is within the affected ranges, indicating potential exposure if those files originate from untrusted sources.
A user is affected if they have Foxit PDF Reader or Foxit PDF Editor installed with a version number matching the affected ranges AND the application has PRC file handling capability.
Generated from the published advisory. Verify against your own configuration.
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 · scoped2025.1.0.27937
Users should avoid opening PRC files from untrusted sources or visiting malicious websites until Foxit releases an official patch addressing this vulnerability.
Foxit PDF Reader/Pdf Editor 2025.1.0.67943 or later (latest stable release)
- 1. Identify the currently installed Foxit product (Pdf Reader or Pdf Editor) and note the exact version number.
- 2. Navigate to the official Foxit download page at www.foxit.com to obtain the latest version.
- 3. Download the most recent stable release of Foxit PDF Reader or Pdf Editor.
- 4. Close all instances of Foxit PDF Reader or Editor before installing the update.
- 5. Run the installer and follow the prompts to complete the upgrade.
- 6. Verify the new version by checking Help > About in the application menu.
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation3.0 h
- Implementation6.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,224.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-9328 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2025-9328 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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