CVE-2025-0911
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 U3D File Parsing Out-Of-Bounds Read Information Disclosure Vulnerability. This vulnerability allows remote attackers to disclose sensitive information 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 parsing of U3D 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-25957.
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 confidenceAn out-of-bounds read vulnerability exists in PDF-XChange Editor's U3D file parser due to insufficient validation of user-supplied data during parsing. The lack of bounds checking allows reading past the end of an allocated object, leading to information disclosure. While this flaw alone enables disclosure, it can be chained with other vulnerabilities to achieve arbitrary code execution in the current process context.
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.5.0.393CVSS 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 the presence of PDF-XChange Editor in the system by searching for the executable file (PDFXEdit.exe) in typical installation locations such as C:\Program Files\PDF-XChange\ or by checking Add/Remove Programs in Windows Control PanelAffected if PDF-XChange Editor is found on the system
-
Determine the installed version numberRight-click on PDFXEdit.exe, select Properties, then view the Details tab to find the File Version, or run the application and navigate to Help > About to display the version informationAffected if The version displayed is lower than 10.5.0.393 (for example, 10.4.x, 10.3.x, or earlier)
-
Confirm U3D parsing capability is presentAttempt to open a PDF file containing U3D 3D content or check if the application has U3D-related DLLs (such as U3D.dll or similar) present in the installation directoryAffected if U3D parsing modules are present in the application and the version is below 10.5.0.393
-
Check for recent PDF files with U3D contentSearch the file system for PDF files that may contain embedded U3D objects, typically identified by searching for files with .pdf extension and examining them with a hex editor or PDF parsing tool for U3D stream objectsAffected if The system contains PDF files with embedded U3D content and the installed PDF-XChange Editor version is below 10.5.0.393
The system is affected if PDF-XChange Editor is installed with a version lower than 10.5.0.393 and the application is used to open PDF files containing U3D 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 · scoped10.5.0.393
Apply vendor-supplied patches for PDF-XChange Editor immediately. Until patched, instruct users to avoid opening untrusted PDF files or visiting malicious pages that may deliver crafted U3D content.
PDF-XChange Editor version 10.5.0.393 or later
- Open PDF-XChange Editor and navigate to Help > About to verify the current version is below 10.5.0.393
- Close PDF-XChange Editor and any associated processes
- Navigate to the official PDF-XChange website (www.tracker-software.com) or use their official download page to obtain version 10.5.0.393 or later
- Download the installer for the latest PDF-XChange Editor version
- Run the installer and complete the upgrade process, following the on-screen prompts
- After installation, verify the version by checking Help > About to confirm the installed version is 10.5.0.393 or higher
- Exercise caution when opening untrusted U3D files or PDF documents from untrusted sources
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation3.0 h
- Implementation8.0 h
- Testing5.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,040.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-0911 — 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-0911 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