CVE REMEDIATION GUIDE
Priority reviewHighFixed-version data available

CVE-2026-22200 remediation guide

Enhancesoft osTicket, osticket

Enhancesoft osTicket versions 1.18.x prior to 1.18.3 and 1.17.x prior to 1.17.7 contain an arbitrary file read vulnerability in the ticket PDF export functionality. A remote attacker can submit a ticket containing crafted rich-text HTML that includes PHP filter expressions which are insufficiently sanitized before being processed by the mPDF PDF generator during export. When the attacker exports the ticket to PDF, the generated PDF can embed the contents of attacker-selected files from the server filesystem as bitmap images, allowing disclosure of sensitive local files in the context of the...

Open CVE record
ProductEnhancesoft osTicket, osticket
Affected versions>= 1.18.0 < 1.18.3, >= 1.17.0 < 1.17.7, >= 1.17 < 1.17.7, >= 1.18 < 1.18.3
Fixed versions1.17.7, 1.18.3
Priority basisPriority · CVSS 8.7 · EPSS 73.1%
01

Identify the affected asset

Confirm whether Enhancesoft osTicket, osticket is installed, record the deployed version and installation path, and identify exposed interfaces.

  • Record the product name, package or appliance identifier, and installed version.
  • Identify internet-facing, administrative, API, and internal access paths.
  • Preserve the pre-change configuration and relevant service logs.
02

Validate the affected-version match

Compare the deployed version with the affected range: >= 1.18.0 < 1.18.3, >= 1.17.0 < 1.17.7, >= 1.17 < 1.17.7, >= 1.18 < 1.18.3. Treat incomplete inventory results as unresolved.

03

Prioritize with independent signals

FIRST EPSS indicates an elevated probability of exploitation. Combine this signal with asset criticality, exposure, compensating controls, and business impact.

04

Apply supported remediation

Follow the vendor advisory or supported update path. Current fixed-version status: 1.17.7, 1.18.3. Preserve configuration and rollback material before change.

05

Verify the result

Confirm the resulting version, service health, authentication and access paths, monitoring coverage, and relevant security logs.

  • Confirm the expected version and package state.
  • Run a functional health check for critical service paths.
  • Review authentication, error, application, and security monitoring logs.
  • Reassess exposure if the supported fix cannot be applied.

Operational boundary

This page does not replace the vendor advisory, support contract, change-management process, or recovery plan. Do not infer that an asset is unaffected from an incomplete inventory query or a missing fixed-version field.

CVE-2026-22200 Remediation Guide | SECUFOCUS NOW