CVE-2025-0910
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 Write 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 parsing of U3D files. The issue results from the lack of proper validation of user-supplied data, which can result in a write past the end of an allocated object. An attacker can leverage this vulnerability to execute code in the context of the current process. Was ZDI-CAN-25748.
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 · moderate confidenceA remote code execution vulnerability exists in PDF-XChange Editor's U3D (Universal 3D) file parsing component. The flaw stems from insufficient validation of user-supplied data during U3D file parsing, leading to an out-of-bounds write that allows attackers to write past the end of an allocated memory object and execute arbitrary code in the context of the current 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< 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.
-
Identify PDF-XChange Editor installationCheck for the presence of PDF-XChange Editor on the system. Common installation paths: C:\Program Files\PDF-XChange Editor\ or C:\Program Files (x86)\PDF-XChange Editor\. Look for executable files like PDFXCview.exe or PDFXEdit.exe in these directories.Affected if PDF-XChange Editor is found installed on the system
-
Determine installed version numberOnce installed, right-click the PDF-XChange Editor executable (PDFXCview.exe or PDFXEdit.exe), select Properties, then go to the Details tab to view the File Version. Alternatively, open the application, go to Help > About to display the version information.Affected if The version number is less than 10.5.0.393
-
Verify U3D parsing capability is presentCheck the application installation directory for U3D-related DLL files that handle 3D content parsing. Look for files containing 'u3d' in the filename within the PDF-XChange Editor program folder.Affected if U3D parsing DLLs are present in the installation directory
-
Confirm if application processes PDF files with 3D contentInspect recent PDF files opened by the application or check default file associations. Look for PDF files that may contain embedded 3D objects, U3D streams, or 3D annotations. These are typically created using CAD software or 3D modeling tools.Affected if PDF files containing U3D or 3D content have been opened or can be opened by the application
A user is affected if PDF-XChange Editor version 10.5.0.393 or higher is NOT installed and the application is used to open PDF files containing U3D or 3D 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
Users should avoid opening untrusted or unexpected PDF files, particularly those containing 3D content, and apply vendor patches or upgrades to PDF-XChange Editor when available. Consider disabling 3D content rendering or using application sandboxing as additional layers of defense.
10.5.0.393
- Upgrade PDF-XChange Editor to version 10.5.0.393 or later
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation8.0 h
- Testing8.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,656.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-0910 — 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-0910 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