Quick answers
- Is CVE-2026-38446 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-38446 being exploited in the wild.
- How severe is CVE-2026-38446?
- Medium severity, with a CVSS score of 6.1, published 3 August 2026.
- Which products and versions are affected?
- Enhancesoft LLC osTicket 1.18.3 and earlier.
- Is there a fix for CVE-2026-38446?
- No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.
- How is CVE-2026-38446 attacked?
- It is attacked over the network.
- Am I affected by CVE-2026-38446?
- Check whether anything you run is named in the advisory. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
Technical details
The vulnerability is a stored XSS (CWE-79) in osTicket 1.18.3 affecting the thread entry title field. The root cause is a missing output-encoding layer: the title is sanitized at write time via Format::sanitize() in ThreadEntry::add() (include/class.thread.php), but is rendered without Format::htmlchars() HTML escaping in three templates (include/staff/templates/thread-entry.tmpl.php, include/client/templates/thread-entry.tmpl.php, include/client/templates/thread-export.tmpl.php). An unauthenticated attacker can exploit this by sending a reply or email with a malicious subject line to the helpdesk; the payload is stored and executes when any staff or client views the ticket thread. The vulnerability requires no authentication for email-based submission and minimal authentication for web-based submission. No patch has been released as of the advisory publication date.
Affected products
- Enhancesoft LLC osTicket 1.18.3 and earlier
Timeline
- 2026-08-03: disclosed