Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessAuthenticate to RT as low-privilege user
-
DeliveryUpload crafted file with embedded JavaScript payload
-
ExploitVictim RT user opens inline-served attachment
-
ExecutionJavaScript executes in victim's browser context
-
ImpactExfiltrate session token or perform actions as victim
Vulnerability Assessment
| Weakness |
CWE
OWASP Top 10:2025
A05:2025 - Injection
ASVS 5.0
V1 - Encoding and Sanitization Output encoding, context-aware escaping
MITRE ATT&CK
2 techniques across 2 tactics: Initial Access, Execution The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up. |
| Exploitation Conditions | The attacker must hold a valid RT user account with permission to upload file attachments (PR:L per CVSS vector) - unauthenticated access is insufficient. A second RT user must actively view or download the malicious upload (UI:R); the script does not execute passively on page load of the ticket list. The vulnerable condition is RT's inline content serving behavior, which is present in all affected versions by default and does not require any non-default configuration. Exploitation is bounded by the attacker's ability to create tickets or add attachments and by the requirement that a victim opens the specific attachment. Higher-impact outcomes (admin session hijack) require targeting users with elevated RT roles, which may involve social engineering or waiting for an admin to review a flagged ticket. |
| Impact | The CVSS 5.4 Medium rating with vector AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:N accurately characterizes the risk profile. Exploitation requires an authenticated RT account (PR:L) - ruling out unauthenticated internet attackers - and victim interaction (UI:R), meaning the attack does not fire automatically without a second user engaging with the malicious upload. No EPSS score was provided in the available data. The vulnerability is not listed in the CISA KEV catalog and no public POC has been identified, placing this in a lower-urgency tier despite the scope change. Real-world risk is elevated in enterprise environments where RT users implicitly trust ticket attachments from colleagues, making social engineering trivial. The vendor's recommendation for immediate upgrade across both active release branches (5.0.x and 6.0.x) signals they consider the exposure meaningful. The primary risk is session hijacking or privilege escalation by a malicious insider or compromised low-privilege account targeting higher-privilege RT users such as administrators. |
| Exploit ScenarioDerived | An authenticated RT user with standard ticket attachment privileges uploads a crafted HTML file containing a JavaScript payload (e.g., a session cookie stealer) to a high-traffic ticket visible to administrators. When an RT administrator views or clicks the attachment, the inline-served file executes the script in their browser, exfiltrating their session token to an attacker-controlled endpoint. No public POC has been identified, but the attack is technically straightforward for any user familiar with XSS and requires no special tooling. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Jul 20, 2026
Stored XSS in Best Practical RT (versions 5.0.0-5.0.9 and 6.0.0-6.0.2) allows any authenticated user with file upload permissions to embed malicious JavaScript in an uploaded file that executes in the browser session of any RT user who later views or downloads that content. The root cause is RT serving uploaded files inline rather than forcing browser download via Content-Disposition: attachment, enabling browsers to render and execute embedded scripts. Vendor-released patches 5.0.10 and 6.0.3 are available (released 2026-05-20); no public exploit identified at time of analysis.
RemediationAI
Upgrade to RT 5.0.10 or RT 6.0.3 immediately, as recommended by the vendor. The RT 6.0.3 release tarball is available at https://download.bestpractical.com/pub/rt/release/rt-6.0.3.tar.gz (SHA-256: 117b53e7a46e82ade662050d98920f1255865ca873d6bec80036085b17dd3dc6). Users on the 6.0.x branch should also apply the separate patch at https://github.com/bestpractical/rt/commit/525547751b76cc422015960bae3056f4e8d4351f.patch to address CVE-2026-41073 (TSV export header injection inadvertently omitted from 6.0.3; will be included in 6.0.4). If an immediate upgrade is not feasible, restrict file upload permissions to the minimum set of trusted users as a compensating control - this does not eliminate the flaw but reduces the attacker pool. Note that restricting upload permissions may impact normal ticket workflows. The full vendor advisory is at https://github.com/bestpractical/rt/security/advisories/GHSA-x576-pvwp-c2qv.
Affected VersionsENISA
Affected Packages
Source: OSV (Open Source Vulnerabilities)
Affects your stack
Affects 2 packages in euvd
Checking this CVE against your own stacks and servers is part of the Basic plan and up.
Technical ContextAI · show details
RT (Request Tracker) is an enterprise issue and ticket tracking system developed by Best Practical Solutions, commonly used by IT operations, legal, and support teams. The CPE cpe:2.3:a:bestpractical:rt:*:*:*:*:*:*:*:* covers all RT application instances. The vulnerability is classified as CWE-79 (Improper Neutralization of Input During Web Page Generation - Stored XSS), specifically arising from the HTTP response Content-Disposition or Content-Type header being set to inline when serving user-uploaded attachments. This allows browsers to interpret and execute HTML or JavaScript embedded within uploaded files rather than prompting the user to save the file locally. The scope change (S:C in CVSS) is characteristic of stored XSS: the injected script runs in a different user's browser security context, not the attacker's.
Know when Rt gets its next vulnerability
- Watch products and get an email when something new is published
- Check this CVE against your own stack and servers
- Exploit and PoC references, threat intelligence from 22 sources
No credit card · 7-day full trial
Severity by source
AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:N
Authenticated upload (PR:L) over network (AV:N); victim must open file (UI:R); XSS executes in victim's browser scope (S:C) with limited confidentiality and integrity impact.
Primary rating from Vendor (GitHub_M).
CVSS VectorVendor: GitHub_M
Lifecycle Timeline
1DescriptionCVE.org
RT is an open source, enterprise-grade issue and ticket tracking system. Versions 5.0.0 and 6.0.0 and above, prior to both 5.0.10 and 6.0.3 contain a Cross-Site Scripting (XSS) vulnerability where uploaded content is served inline rather than as an attachment. An authenticated user who can upload content can include JavaScript in the upload that will execute in the browser session of any RT user who later views or downloads it. This issue has been fixed in versions 5.0.10 and 6.0.3.
Threat Intelligence Overview
How this decision was reached
The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.
What every action level means
SSVC AssessmentENISA
Priority Score
Attack Technique
Cross-Site Scripting occurs when an application accepts untrusted data and sends it to a web browser without proper validation or encoding.
Privilege escalation and information disclosure in Best Practical's Request Tracker (RT) 6.0.0-6.0.2 and versions before
Authenticated SQL injection in Best Practical's Request Tracker (RT) ticketing system affects versions 5.0.0-5.0.9 and 6
Authentication bypass in Best Practical's Request Tracker (RT) versions 5.0.9 and prior, and 6.0.0 through 6.0.2, allows
Cross-site request forgery in Best Practical Request Tracker (RT) versions 6.0.0 through 6.0.2 allows remote attackers t
Request Tracker (RT) 3.8.x before 3.8.17 and 4.0.x before 4.0.13 does not properly restrict access to private callback c
Cross-site request forgery (CSRF) vulnerability in Request Tracker (RT) 3.8.12 and other versions before 3.8.15, and 4.0
Reflected Cross-Site Scripting in Best Practical RT versions 5.0.4-5.0.9 and 6.0.0-6.0.2 allows an unauthenticated attac
Reflected Cross-Site Scripting in RT (Request Tracker) 6.0.0 through 6.0.2 allows an unauthenticated network attacker to
Request Tracker (RT) 3.8.x before 3.8.17 and 4.0.x before 4.0.13 allows remote authenticated users with the permissions
Request Tracker (RT) 4.x before 4.0.13 does not properly enforce the DeleteTicket and "custom lifecycle transition" perm
Stored Cross-Site Scripting in Best Practical RT versions 6.0.0 through 6.0.2 allows an authenticated attacker with writ
Algorithmic complexity vulnerability in Email::Address::List before 0.02, as used in RT 4.2.0 through 4.2.2, allows remo
EUVD-2026-46078
NVD
CVE.org
EPSS
Vulnrichment
GitHub
VulDB
Exploit-DB