CVE-2026-22200
CVE-2026-22200 is a high-severity vulnerability in Enhancesoft osTicket (CVSS 4.0 CVSS-B score 8.7), classified as CWE-74 (Injection). It is not in the CISA Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment rates its exploitation as none. As of 2026-11-22, EPSS estimates a 73.6% probability of exploitation in the next 30 days, in the 99th percentile of scored CVEs.
Updated
- CVSS 4.0
- 8.7 HIGH
- EPSS
- 73.6% (99th pct)
- CISA KEV
- Not listed
- Published
- 2026-01-12
- Weakness
- CWE-74
Description
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 osTicket application user. This issue is exploitable in default configurations where guests may create tickets and access ticket status, or where self-registration is enabled.
Key Findings
as of 2026-11-22- Its current EPSS score (73.6%) is higher than that of 58% of CISA KEV entries.
Severity
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:NOpen in CVSS calculator Remediation Timeline
BOD 26-04, US federal agenciesIf CISA adds it to the KEV catalog: 3 days on a publicly exposed asset, 14 days on other assets.
Deadlines for US federal civilian agencies under Table 1 of CISA BOD 26-04, from the CVE's KEV status (not listed) and CISA's SSVC values (automatable yes, technical impact partial, 2026-01-12).
How the timeline is set
Table 1 of CISA's Binding Operational Directive 26-04 sets the time US federal civilian agencies have to remediate a vulnerability. It depends on four inputs: whether the asset is publicly exposed, whether the CVE is in the KEV catalog, whether an adversary can automate its exploitation, and whether exploitation gives partial or total control of the asset, which SSVC calls technical impact. CISA publishes the last three for every CVE through services such as its Vulnrichment program.
Days are calendar days. The clock starts at whichever comes first: CISA adds the CVE to the KEV catalog, or the agency identifies the vulnerability on an asset and reports it to its Continuous Diagnostics and Mitigation (CDM) dashboard. A publicly exposed asset is accessible to unauthenticated or untrusted entities via public networks, such as the internet.
If CISA adds the CVE to the KEV catalog, the timeline shortens.
Affected Products
| Vendor | Product | Affected versions |
|---|---|---|
| Enhancesoft | Enhancesoft osTicket | 1.18.0 to <1.18.3 1.17.0 to <1.17.7 |
References
5 linksPatches
Exploits & PoCs
Third-party advisories
Release notes
Record Details
- Published
- 2026-01-12
- Last updated
- 2026-11-08
- Assigner (CNA)
- VulnCheck
- Credited to
- Naveen Sunkavally, Horizon3.ai
CVE record data © The MITRE Corporation, used under the CVE Terms of Use. Exploited-in-the-wild data from the CISA Known Exploited Vulnerabilities catalog (CC0). Exploit prediction scores by FIRST EPSS (first.org/epss). Alert titles and links from CISA cybersecurity alerts. This site is not affiliated with or endorsed by MITRE, NVD, CISA, or FIRST.