CVE-2025-0901
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 · uneditedPDF-XChange Editor Doc Object Out-Of-Bounds Read Remote Code Execution Vulnerability. This vulnerability allows remote attackers to execute arbitrary code on affected installations of PDF-XChange Editor. 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 handling of Doc objects. 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-25372.
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 confidenceOut-of-bounds read vulnerability in PDF-XChange Editor's Doc object handling due to insufficient validation of user-supplied data. The flaw allows reading past the end of an allocated buffer, which can be leveraged by attackers to achieve remote code execution in the context of the current process. User interaction (opening a malicious file or visiting a malicious page) is required for exploitation.
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< 10.4.1.389CVSS 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
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- Required
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/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.
-
Verify PDF-XChange Editor is installedCheck for PDF-XChange Editor installation on the system. Common install locations: C:\Program Files\PDF-XChange\PDF-XChange Editor or C:\Program Files (x86)\PDF-XChange\PDF-XChange Editor. On Windows, also check Add/Remove Programs or Settings > Apps.Affected if PDF-XChange Editor is not present on the system
-
Determine installed version numberOpen PDF-XChange Editor and navigate to Help > About, or right-click the executable file and select Properties > Details to view the version. You can also find this in Windows Add/Remove Programs.Affected if Unable to retrieve the installed version number
-
Compare version against affected rangeCompare the installed version to 10.4.1.389. Any version lower than 10.4.1.389 falls within the affected range.Affected if Installed version is less than 10.4.1.389
-
Identify PDF processing contextThe vulnerability is in the Doc object handling which is used when opening PDF files. Check if the application is used to open PDF documents, particularly from untrusted or unknown sources.Affected if The Doc object processes user-supplied PDF data
The environment is affected if PDF-XChange Editor is installed with a version lower than 10.4.1.389 and the Doc object is used to process PDF files.
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 · scoped10.4.1.389
Update PDF-XChange Editor to the latest version once the vendor releases a patch. Until then, avoid opening untrusted PDF files or visiting untrusted websites that could deliver malicious PDF content.
10.4.1.389
- Navigate to the official PDF-XChange website (www.tracker-software.com) or your existing PDF-XChange Editor installation to obtain the latest version
- Download PDF-XChange Editor version 10.4.1.389 or later from the official vendor source
- Close any running instances of PDF-XChange Editor
- Run the installer and follow the on-screen prompts to complete the upgrade
- After installation, verify the version by navigating to Help > About PDF-XChange Editor to confirm the installed version is 10.4.1.389 or higher
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation1.0 h
- Testing3.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 $2,224.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-0901 — 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-0901 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