Quick answers
- Is CVE-2026-105454 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-105454 being exploited in the wild.
- How severe is CVE-2026-105454?
- Informational severity, published 30 October 2026.
- Which products and versions are affected?
- Best Practical Solutions Request Tracker 5.0.0 through 5.0.10, 6.0.0 through 6.0.3.
- Is there a fix for CVE-2026-105454?
- Yes: fixed in Request Tracker 5.0.11, 6.0.4. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-105454 attacked?
- It is attacked over the network, in a web application.
- Am I affected by CVE-2026-105454?
- Check whether you run Best Practical Solutions Request Tracker at an affected version. 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.
How to fix
- Fixed in: Request Tracker 5.0.11, 6.0.4
Technical details
The vulnerability is an improper neutralization of input during web page generation (CWE-79) where RT's automatic link creation fails to HTML-escape URLs placed in link attributes. An attacker can craft a malicious URL in HTML content that breaks out of the href attribute and injects a script tag. This stored XSS executes in the context of any user viewing the ticket history, including unauthenticated email senders on public queues with CreateTicket or ReplyToTicket permissions to Everyone.
Affected products
- Best Practical Solutions Request Tracker 5.0.0 through 5.0.10, 6.0.0 through 6.0.3
Timeline
- 2026-10-30: disclosed