dbcve.org
Pdf Xchange EditorApplication · Pdf Xchange

CVE-2022-41147

HIGH · 7.8 CVSS v3.1 Published 2023-01-26
Fix available
A fix is available. Upgrade to 9.5.366.0 or later.
See remediation →
81/100
Remediation priority · High
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
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. Crafted data in a U3D file can trigger a write 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-18286.

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

Buffer overflow vulnerability in PDF-XChange Editor's U3D file parser. Attackers craft malicious U3D files embedded in PDFs that cause a write-past-end-of-buffer condition, enabling arbitrary code execution in the context of the current process. Requires user to open a malicious file.

MitigationApply vendor patch/upgrade to latest PDF-XChange Editor version. Avoid opening untrusted PDF files from unknown sources until patch is applied.

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:< 9.5.366.0

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
Local
Complexity
Low
Privileges
None
User interaction
Required
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:L/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. Identify PDF-XChange Editor installation
    Open Windows Control Panel > Programs and Features, or use command: Get-ItemProperty 'HKLM:\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\*' | Where-Object {$_.DisplayName -like '*PDF-XChange*'}
    Affected if PDF-XChange Editor is installed on the system
  2. Determine installed version number
    In Programs and Features, locate PDF-XChange Editor and note the Version column. Alternatively, right-click the application executable (PDFXCview.exe or PDFXEdit.exe) in the program directory, select Properties, and check the Details tab for Product Version
    Affected if The version displayed is lower than 9.5.366.0
  3. Verify U3D file parsing capability
    Open PDF-XChange Editor, go to File > Preferences > File Associations, or check if the application can open PDF files containing 3D content (U3D). Default installations support U3D rendering without additional configuration
    Affected if U3D parsing is available (default enabled) and version is below 9.5.366.0

System is affected if PDF-XChange Editor version 9.5.366.0 or higher is NOT installed and the application can process PDF files with embedded U3D content.

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 9.5.366.0 or later
Fixed in 9.5.366.0
Interim mitigation

Apply vendor patch/upgrade to latest PDF-XChange Editor version. Avoid opening untrusted PDF files from unknown sources until patch is applied.

Recommended fix High confidence

9.5.366.0 or later

  1. Check the current version of PDF-XChange Editor by clicking Help > About in the application menu
  2. Navigate to the official PDF-XChange website (www.tracker-software.com) and locate the downloads section
  3. Download the latest version of PDF-XChange Editor (version 9.5.366.0 or later)
  4. Run the installer and follow the on-screen prompts to complete the upgrade
  5. Verify the installation was successful by checking Help > About to confirm the version is 9.5.366.0 or higher
  6. Avoid opening untrusted U3D files or visiting untrusted web pages until the update 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
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA1.0 h
10.0 hours of engineering $1,750
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2022-41147 — 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-2022-41147 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