dbcve.org
Pdf Xchange EditorApplication · Pdf Xchange

CVE-2022-37352

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 parsing of WMF files. Crafted data in a WMF file can trigger a read past the end of an allocated buffer. An attacker can leverage this in conjunction with other vulnerabilities to execute arbitrary code in the context of the current process. Was ZDI-CAN-17638.

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

This is an out-of-bounds read vulnerability in PDF-XChange Editor's WMF (Windows Metafile) file parser. Crafted WMF files with malformed data allow reading past the end of an allocated buffer, potentially disclosing sensitive memory contents. While this vulnerability alone enables information disclosure, it can be chained with other flaws to achieve arbitrary code execution.

MitigationApply the vendor patch for CVE-2022-37352 when available. Until then, restrict user ability to open untrusted WMF files and educate users about not opening files from untrusted sources.

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. Identify if PDF-XChange Editor is installed
    Check the installed programs list in Windows Control Panel > Programs and Features, or use PowerShell: Get-ItemProperty 'HKLM:\Software\Microsoft\Windows\CurrentVersion\Uninstall\*' | Where-Object {$_.DisplayName -like '*PDF-XChange*Editor*'}
    Affected if PDF-XChange Editor is present on the system
  2. Determine the installed version of PDF-XChange Editor
    Right-click the application shortcut, select Properties, and check the Details tab for version information. Alternatively, right-click the executable file (usually in C:\Program Files\PDF-XChange\ or C:\Program Files (x86)\PDF-XChange\) and view Properties > Details.
    Affected if The version shown is exactly 9.3.361.0
  3. Confirm WMF file handling capability
    Open PDF-XChange Editor and attempt to import or open a WMF file (Windows Metafile). Check if the application can process WMF files through File > Open or via insert/import functionality.
    Affected if The application can open or process WMF files (the vulnerable parser is invoked when WMF files are handled)

You are affected only if PDF-XChange Editor version 9.3.361.0 is installed AND the application processes WMF files, as the out-of-bounds read occurs in the WMF parser when handling malformed WMF data.

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 patch for CVE-2022-37352 when available. Until then, restrict user ability to open untrusted WMF files and educate users about not opening files from untrusted sources.

Recommended fix Moderate confidence

Latest available version from www.tracker-software.com (verify version > 9.3.361.0 and containing the security fix)

  1. 1. Visit the official Tracker Software website at www.tracker-software.com to check for the latest version of PDF-XChange Editor.
  2. 2. Navigate to the downloads or support section for PDF-XChange Editor.
  3. 3. Download and install the latest available version of PDF-XChange Editor.
  4. 4. Verify the installed version matches or exceeds the fixed release that addresses CVE-2022-37352.
  5. 5. Re-scan or re-test any WMF files that were previously opened with version 9.3.361.0 to ensure they no longer trigger the vulnerability.

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
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
17.0 hours of engineering $3,000
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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