dbcve.org
Pdf Xchange EditorApplication · Pdf Xchange

CVE-2022-37368

MEDIUM · 5.5 CVSS v3.1 Published 2023-03-29
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
58/100
Remediation priority · Elevated
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 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 handling of Doc objects. By performing actions in JavaScript, an attacker can trigger 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-17728.

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 in PDF-XChange Editor's Doc object handling allows remote attackers to disclose sensitive information via maliciously crafted PDF files containing specific JavaScript actions. The vulnerability requires user interaction (opening a malicious file) and can leak memory contents beyond allocated buffers.

MitigationApply the vendor-supplied patch or update PDF-XChange Editor to the latest version. Until patched, avoid opening untrusted PDF files and disable JavaScript execution in the application if possible.

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.3.361.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
None
Availability
None

CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:N/A:N

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 installation
    Check for PDF-XChange Editor in the installed programs list (Windows Control Panel > Programs and Features) or look for the executable file (PDFXCview.exe or PDFXEdit.exe) in Program Files directory.
    Affected if PDF-XChange Editor is installed on the system
  2. Identify installed version
    Right-click the PDF-XChange Editor executable (PDFXCview.exe or PDFXEdit.exe), select Properties, and check the Details tab for the version number. Alternatively, open the application and go to Help > About.
    Affected if The installed version is 9.3.361.0 exactly as listed in affected versions
  3. Verify JavaScript is enabled in the application
    Open PDF-XChange Editor, go to Edit > Preferences (or Options), navigate to JavaScript section and check if JavaScript execution is enabled/allowed.
    Affected if JavaScript is enabled in the application settings, as the vulnerability exploits specific JavaScript actions in malicious PDFs
  4. Check for recent PDF file handling behavior
    Review recently opened PDF files or check email attachments that were opened, particularly from untrusted sources, as the vulnerability requires user interaction to open a malicious file.
    Affected if Untrusted or unexpected PDF files have been opened recently, especially from unknown senders

You are affected if PDF-XChange Editor version 9.3.361.0 is installed AND JavaScript execution is enabled in the application, as the vulnerability requires both the specific version and user interaction with a malicious PDF file containing JavaScript actions.

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
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Apply the vendor-supplied patch or update PDF-XChange Editor to the latest version. Until patched, avoid opening untrusted PDF files and disable JavaScript execution in the application if possible.

Recommended fix Moderate confidence

Latest available version of PDF-XChange Editor (newer than 9.3.361.0)

  1. Navigate to the official PDF-XChange Editor website at www.tracker-software.com
  2. Locate the downloads or updates section for PDF-XChange Editor
  3. Download the latest stable version of PDF-XChange Editor
  4. Close any running instances of PDF-XChange Editor
  5. Install the downloaded update following the installation wizard prompts
  6. Restart the application if not automatically prompted

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

Fix this in Pdf Xchange Editor Scoped from the published advisory
  • Consultation1.0 h
  • Implementation1.0 h
  • Testing2.0 h
  • Review / QA1.0 h
5.0 hours of engineering $860
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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