Mantisbt/Mantisbt (<= 2.28.1) — CraftedSignal Threat Feedhttps://feed.craftedsignal.io/products/mantisbt/mantisbt--2.28.1/Trending threats, MITRE ATT&CK coverage, and detection metadata. Fed continuously.Hugoenhello@craftedsignal.iohello@craftedsignal.ioMon, 11 May 2026 19:42:20 +0000MantisBT Vulnerable to Stored XSS in File Downloadhttps://feed.craftedsignal.io/briefs/2026-05-mantisbt-xss/Mon, 11 May 2026 19:42:20 +0000hello@craftedsignal.iohttps://feed.craftedsignal.io/briefs/2026-05-mantisbt-xss/MantisBT is vulnerable to stored cross-site scripting (XSS) via file_download.php by using the `show_inline=1` parameter with a valid CSRF token to upload a crafted XHTML attachment referencing a JavaScript attachment, leading to arbitrary code execution.MantisBT, a web-based bug tracking system, is vulnerable to a stored cross-site scripting (XSS) attack. The vulnerability exists in the file_download.php script. By exploiting this flaw, an attacker can inject malicious JavaScript code into the application, which will be executed in the context of other users’ browsers when they access the affected functionality. The vulnerability is triggered when processing file downloads, specifically when the show_inline=1 parameter is used in conjunction with a valid file_show_inline_token CSRF token. This allows an attacker to upload a crafted XHTML attachment that references a JavaScript attachment. The vulnerability affects MantisBT versions 2.28.1 and earlier. This can lead to account takeover, sensitive data leakage, and other malicious activities.

Attack Chain

  1. Attacker authenticates to MantisBT as a user with permissions to upload attachments.
  2. Attacker crafts a malicious JavaScript file (e.g., evil.js) containing the XSS payload.
  3. Attacker crafts a malicious XHTML file (e.g., evil.xhtml) that includes the JavaScript file using <script src="evil.js"></script>.
  4. Attacker obtains a valid CSRF token for the file_show_inline_token parameter.
  5. Attacker uploads both the evil.js and evil.xhtml files as attachments to a MantisBT issue.
  6. Attacker crafts a request to file_download.php with the show_inline=1 parameter, the valid CSRF token, and the file IDs of the uploaded evil.xhtml attachment.
  7. A victim user clicks a link (or is redirected) to the crafted file_download.php URL.
  8. The server serves the evil.xhtml file inline, which executes the embedded evil.js JavaScript in the victim’s browser, allowing the attacker to perform actions on behalf of the victim.

Impact

Successful exploitation of this vulnerability allows an attacker to execute arbitrary JavaScript code in the context of a victim’s browser. This can lead to a variety of malicious activities, including session hijacking, defacement of the MantisBT interface, theft of sensitive information, or further exploitation of the MantisBT server or the victim’s machine. Given the nature of bug tracking systems, successful exploitation could impact multiple users within an organization, potentially leading to widespread compromise.

Recommendation

  • Apply the patch provided by MantisBT (26647b2e68ba30b9d7987d4e03d7a16416684bc2) to remediate the vulnerability.
  • Deploy the Sigma rule “Detect MantisBT XSS via file_download.php” to identify potential exploitation attempts.
  • Monitor web server logs for requests to file_download.php with the show_inline=1 parameter and potentially malicious content in the request.
]]>highthreatxssmantisbtgithub advisory