CVE-2026-105454: Stored XSS via crafted URLs in HTML ticket content in Request Tracker
RT's automatic link creation for URLs in HTML ticket content does not HTML-escape the URL it places in the link. A URL crafted to break out of the link's address can add a script that runs when the ticket history is displayed, with no further action by the viewer. Anyone who can add HTML content to a ticket can plant it. That includes an unauthenticated sender of HTML email to any queue that grants CreateTicket or ReplyToTicket to Everyone, which is routine for a queue that accepts mail from the public. The script runs in the session of any user who views the ticket, and can act in RT with that user's authority.
This issue was fixed in version 5.0.11 and 6.0.4
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade
Request Trackerto a version that resolves this vulnerability.Fixed in 5.0.11 - Upgrade
Upgrade
Request Trackerto a version that resolves this vulnerability.Fixed in 6.0.4
Frequently Asked Questions
Which deployments are most exposed to unauthenticated exploitation?
Queues that accept HTML email from the public and grant CreateTicket or ReplyToTicket to Everyone are exposed to unauthenticated attackers. An attacker can send a crafted HTML email that creates a ticket or reply containing the malicious URL.
What user interaction is required for the payload to execute?
The attacker must be able to add HTML content to a ticket, but the viewer needs only to display the ticket history. No additional click or action by the viewer is required.
What can a successful payload do?
The injected script runs in the session of the user viewing the ticket and can act in Request Tracker with that user's authority. The resulting impact depends on the permissions of the viewing user.
What versions contain the fix?
The issue was fixed in Request Tracker versions 5.0.11 and 6.0.4.