CVE-2026-38446
Received Received - Intake

Stored XSS in osTicket 1.18.3

Vulnerability report for CVE-2026-38446, including description, CVSS score, EPSS score, affected products, exploitability, helpful resources, and attack-flow context.

Publication date: 2026-08-03

Last updated on: 2026-08-03

Assigner: MITRE

Description

A stored cross-site scripting (XSS) vulnerability exists in osTicket 1.18.3 due to improper sanitization of the thread entry title field. User-controlled input in the title is stored without adequate HTML escaping and later rendered in multiple staff-facing templates without proper output encoding. An attacker can inject arbitrary JavaScript by submitting a crafted ticket reply or email with a malicious subject line.

CVSS Scores

EPSS Scores

Probability:
Percentile:

Meta Information

Published
2026-08-03
Last Modified
2026-08-03
Generated
2026-08-04
AI Q&A
2026-08-03
EPSS Evaluated
N/A
NVD
EUVD

Affected Vendors & Products

Showing 1 associated CPE
Vendor Product Version / Range
osticket osticket 1.18.3

Helpful Resources

Exploitability

CWE
CWE Icon
KEV
KEV Icon
CWE ID Description
CWE-79 The product does not neutralize or incorrectly neutralizes user-controllable input before it is placed in output that is used as a web page that is served to other users.

Attack-Flow Graph

AI Quick Actions

Instant insights powered by AI
Executive Summary

This is a stored cross-site scripting (XSS) vulnerability in osTicket version 1.18.3. It occurs because user input in the thread entry title field is not properly sanitized before being stored in the database. Later, when this data is displayed in staff-facing templates, it is rendered without proper output encoding, allowing malicious JavaScript to execute in the browser of affected users.

Detection Guidance

To detect this vulnerability, inspect osTicket 1.18.3 for improperly sanitized thread entry titles. Check if user input in ticket replies or email subjects is stored without HTML escaping. Review templates where titles are rendered to confirm missing output encoding. Manual review of database entries for malicious scripts in title fields may also help.

Impact Analysis

An attacker could exploit this to inject arbitrary JavaScript by submitting a malicious ticket reply or email with a crafted subject line. This could lead to session hijacking, defacement of the osTicket interface, theft of sensitive data, or redirection to malicious websites when staff view the affected ticket or thread.

Compliance Impact

This vulnerability could lead to unauthorized access to personal data, violating GDPR's data protection principles and HIPAA's security requirements. If exploited, it may result in data breaches, unauthorized disclosure of protected health information, or other compliance violations depending on the data processed by osTicket.

Mitigation Strategies

Upgrade osTicket to a patched version if available. Implement strict input validation for thread entry titles and email subjects. Apply HTML escaping or output encoding when rendering titles in staff-facing templates. Monitor for suspicious ticket activity or unauthorized script execution.

Chat Assistant

Ask questions about this CVE
Hi! I’m here to help you understand CVE-2026-38446. Ask me anything about the vulnerability, its impact, or mitigation strategies.
0/70

EPSS Chart