dbcve.org
Pdf Xchange EditorApplication · Pdf Xchange

CVE-2025-0909

HIGH · 8.8 CVSS v3.1 Published 2025-02-11
Fix available
A fix is available. Upgrade to 10.5.0.393 or later.
See remediation →
95/100
Remediation priority · Urgent
Remotely reachable No privileges

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 · unedited
PDF-XChange Editor XPS 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 XPS 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-25678.

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 confidence

An out-of-bounds read vulnerability exists in PDF-XChange Editor's XPS 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 classified as information disclosure, this can be chained with other vulnerabilities to achieve arbitrary code execution in the current process context.

MitigationAvoid opening untrusted XPS files or visiting untrusted web pages until PDF-XChange Editor releases an official patch. Consider using alternative PDF viewers or disabling XPS file handling as a temporary workaround.

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
Pdf Xchange EditorApplication
Affected:< 10.5.0.393

CVSS 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 checks

Work through these to decide whether this CVE applies to you.

  1. Confirm PDF-XChange Editor is installed
    Open Windows Settings > Apps & features, or use Control Panel > Programs and Features, and look for 'PDF-XChange Editor' in the installed programs list. Alternatively, check the installation directory (commonly C:\Program Files\PDF-XChange Editor or C:\Program Files (x86)\PDF-XChange Editor).
    Affected if PDF-XChange Editor is present on the system
  2. Determine the installed version number
    Right-click on the PDF-XChange Editor executable (PDFXCview.exe or similar) in the installation folder, select Properties, then go to the Details tab to see the Product Version. Or, launch the application and go to Help > About to display the version information.
    Affected if The version displayed is lower than 10.5.0.393 (for example, 10.4.x.x, 10.3.x.x, or earlier)
  3. Verify XPS file handling capability is enabled
    PDF-XChange Editor includes native XPS parsing support. Check if XPS filter/directory handlers are present by looking for PDF-XChange Editor in the Windows default programs list, or attempt to open a standard XPS file with the application to confirm it processes XPS files.
    Affected if The application can open and parse XPS files (which is enabled by default)

The system is affected if PDF-XChange Editor is installed with any version lower than 10.5.0.393 and the application is capable of opening XPS files, as the vulnerability triggers during XPS file parsing.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 · scoped
Upgrade available Upgrade to 10.5.0.393 or later
Fixed in 10.5.0.393
Interim mitigation

Avoid opening untrusted XPS files or visiting untrusted web pages until PDF-XChange Editor releases an official patch. Consider using alternative PDF viewers or disabling XPS file handling as a temporary workaround.

Recommended fix High confidence

PDF-XChange Editor 10.5.0.393

  1. Verify the current version of PDF-XChange Editor by clicking Help > About
  2. Download PDF-XChange Editor version 10.5.0.393 or later from the vendor's official website
  3. Close all instances of PDF-XChange Editor
  4. Run the installer and follow the prompts to upgrade to the fixed version
  5. After installation, verify the new version by checking Help > About to confirm version 10.5.0.393 or higher is installed
  6. Avoid opening untrusted XPS files from unknown sources as a defensive measure until the patch is applied

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Pdf Xchange Editor Scoped from the published advisory
  • Consultation3.0 h
  • Implementation4.0 h
  • Testing6.0 h
  • Review / QA2.0 h
15.0 hours of engineering $2,580
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,128.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-0909 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-0909 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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