CVE-2025-9324
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 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-26802.
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, potentially exposing sensitive memory contents. While the primary impact is information disclosure, the advisory notes this can be chained with other vulnerabilities for code execution.
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
- 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 checksWork through these to decide whether this CVE applies to you.
-
Confirm Foxit PDF product is installedOpen Windows Settings > Apps & Features or use 'Get-ItemProperty HKLM:\Software\Microsoft\Windows\CurrentVersion\Uninstall\* | Select-Object DisplayName, DisplayVersion' to list installed softwareAffected if Foxit PDF Reader or Foxit PDF Editor appears in the installed programs list
-
Identify the exact Foxit versionRight-click the Foxit application icon, select 'About Foxit [Reader/Editor]' or go to Help > About to view the exact version number and buildAffected if Version displayed does not match any of the safe versions listed in the CVE advisory
-
Compare installed version against affected rangesFor Foxit PDF Reader: check if version is < 2025.1.0.27937 or <= 2025.1.0.66692. For Foxit PDF Editor: check if version falls within <=13.1.7.23637, >=2023.1.0.15510 to <=2023.3.0.23028, >=2024.1.0.23997 to <=2024.4.1.27687, =2025.1.0.27937, <=13.1.7.63027, >=2023.1.0.55583 to <=2023.3.0.63083, >=2024.1.0.63682 to <=2024.4.1.66479, or =2025.1.0.66692Affected if Installed version matches any of the listed affected ranges or falls between the bounds specified in the CVE
-
Verify PRC file handler is presentCheck if the Foxit PRC plugin or handler is installed by looking in the Foxit program directory for PRC-related files (such as prc.* or PRC* in the plugins folder) or check File > Open dialog for PRC file type supportAffected if PRC handler files exist and PRC files can be opened within Foxit, indicating the vulnerable component is present
-
Inspect recent PRC file activityReview recently opened PDF files in Foxit or check Windows recently used files for any .prc or .pdf files that may contain embedded PRC content from untrusted sourcesAffected if Users have opened PRC files from untrusted or unknown sources, creating a potential attack vector for this vulnerability
You are affected if Foxit PDF Reader or Foxit PDF Editor is installed with a version matching any of the affected ranges and the PRC file handler is present and functional.
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
Apply the vendor patch from Foxit once available; until then, avoid opening untrusted PRC files and disable the PRC handler if possible. Use caution with PDF files from untrusted sources.
Upgrade to Foxit PDF Reader version 2025.1.0.27937 or later
- 1. Open Foxit PDF Reader application
- 2. Navigate to Help > Check for Updates or About Foxit Reader
- 3. Note the current installed version number
- 4. Download the latest version of Foxit PDF Reader from the official Foxit website (www.foxit.com)
- 5. Run the installer and follow prompts to upgrade to the latest version
- 6. Alternatively, navigate to Foxit's support or downloads page and locate the version 2025.1.0.27937 or later
- 7. Verify the update was successful by checking the version in Help > About Foxit Reader
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation1.0 h
- Testing2.0 h
- Review / QA1.0 h
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 locallyCheck whether your project pulls in CVE-2025-9324 — 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-9324 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