Stored XSS via related ticket subject on RTIR Split and Create Incident forms
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- Fix
- Fixed in 6.0.4
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
- Exploitation: none
- Automatable: no
- Technical impact: partial
Summary
Request Tracker for Incident Response (RTIR) is affected, where the ticket creation forms for splitting a ticket or creating an incident from a report display the related ticket's subject without escaping it. An attacker who emails a report can insert a malicious script into that subject, which then runs in the browser of the staff member using the form and can perform actions in RT with that user's permissions.
Summarized by anthropic/claude-haiku-5.5. Verify details against the original sources.
Read the original description
RTIR's ticket creation forms show the subject of the related ticket when splitting a ticket or creating an incident from a report, and they render that subject without HTML escaping. A ticket subject containing script runs it when a user opens either form. RTIR grants everyone the right to create Incident Reports by default, so an unauthenticated sender of an emailed report can set that subject. The script then runs in the session of the incident handler who creates an incident from the report or splits it, and can act in RT with that user's authority. The issue was fixed in version 6.0.4. RTIR 5.0 is not affected.
Timeline
- CVE published
- First seen by cve.now
- CISA SSVC assessment
Exploitation: none · Automatable: no · Technical impact: partial
- Record last updated
Affected versions
- Best Practical Solutions RT for Incident Response
From 6.0.0 · fixed in 6.0.4