CVE-2025-9323
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 JP2 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 JP2 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-27101.
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 JP2 (JPEG 2000) file parser due to insufficient validation of user-supplied data. The lack of proper bounds checking allows reading past the end of an allocated buffer, exposing sensitive memory contents. While the primary impact is information disclosure, this vulnerability can be chained with other flaws to achieve arbitrary 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< 2025.1.0.27937CVSS 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.
-
Identify Foxit PDF product installationCheck for Foxit PDF Reader or Foxit PDF Editor in installed programs. On Windows, check 'Add or Remove Programs' or look for Foxit Reader.exe / FoxitPDFEditor.exe in Program Files folder.Affected if Foxit PDF Reader or Foxit PDF Editor is installed on the system
-
Determine installed Foxit versionOpen Foxit, go to Help > About Foxit PDF Reader/Editor, or right-click the executable and select Properties > Details to view the version number.Affected if Version is Foxit PDF Reader < 2025.1.0.27937 OR Foxit PDF Editor version matches any of these ranges: <= 13.1.7.23637, >= 2023.1.0.15510 AND <= 2023.3.0.23028, >= 2024.1.0.23997 AND <= 2024.4.1.27687, OR exactly 2025.1.0.27937
-
Confirm JP2 parsing is accessibleThe JP2 (JPEG 2000) image parser is built into Foxit and activates automatically when opening any PDF containing JP2-encoded images. No special configuration needs to be enabled.Affected if The product can open PDF files, meaning the JP2 parsing module is available and active by default
You are affected if Foxit PDF Reader version is below 2025.1.0.27937 or Foxit PDF Editor version falls within any of the specified affected ranges, and you open PDF files containing JP2 image content.
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 refrain from opening untrusted PDF files or visiting malicious websites that deliver malformed JP2 content. Apply vendor patches when released by Foxit.
Upgrade to Foxit PDF Reader/Pdf Editor version 2025.1.0.27937 or later
- 1. Open Foxit PDF Reader or Pdf Editor application
- 2. Navigate to Help > Check for Updates or About Foxit PDF Reader/Editor
- 3. Alternatively, visit the official Foxit download page at www.foxit.com to download the latest version
- 4. Download and install the latest version (2025.1.0.27937 or later)
- 5. Restart the application after updating
- 6. Verify the version by checking Help > About to confirm the update was applied
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation3.0 h
- Implementation8.0 h
- Testing6.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 $5,280.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-9323 — 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-9323 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