CVE-2026-40607
HighCVSS 7.5Exploitation Probability (EPSS)
Low risk34th percentile - higher than 34% of all known CVEs
Summary
MantisBT versions 2.11.0 through 2.28.1 contain a stored XSS vulnerability due to incorrect escaping of a saved filter's owner. An attacker can inject arbitrary HTML if the option to show real user names is enabled.
Risk Assessment
The risk involves executing malicious scripts in the browser of an administrator or other privileged user, potentially leading to session theft or account takeover.
Recommendation
Immediately upgrade to version 2.28.2. If not possible, disable the display of real user names and restrict the ability to save filters publicly.
Other vulnerabilities in MantisBT
See all- CVE-2014-9624High
CAPTCHA bypass vulnerability in MantisBT before version 1.2.19.
- CVE-2017-7615High
MantisBT through 2.3.0 allows arbitrary password reset and unauthenticated admin access via an empty confirm_hash value to verify.php.
- CVE-2014-9572High
MantisBT before 1.2.19 and 1.3.x before 1.3.0-beta.2 does not properly restrict access to /*/install.php, allowing remote attackers to obtain database credentials via the install parameter with the value 4.
- CVE-2014-9280High
The current_user_get_bug_filter function in core/current_user_api.php in MantisBT before 1.2.18 allows remote attackers to execute arbitrary PHP code via the filter parameter.
- CVE-2014-9089High
Multiple SQL injection vulnerabilities in MantisBT before version 1.2.18 in view_all_bug_page.php allow remote attackers to execute arbitrary SQL commands via the sort or dir parameter to view_all_set.php.
- CVE-2014-8554High
SQL injection vulnerability in the mc_project_get_attachments function in api/soap/mc_project_api.php in MantisBT before 1.2.18 allows remote attackers to execute arbitrary SQL commands via the project_id parameter.
- CVE-2014-1609High
Multiple SQL injection vulnerabilities in MantisBT before version 1.2.16 allow remote attackers to execute arbitrary SQL commands via unspecified parameters in various API functions.
- CVE-2026-44657High
Mantis Bug Tracker (MantisBT) prior to version 2.28.2 contains a vulnerability that allows code execution by an attacker. By using the show_inline=1 parameter and a valid file_show_inline_token CSRF token on file_download.php, an attacker can upload a crafted XHTML attachment referencing a JavaScript attachment.
- CVE-2026-44655High
In Mantis Bug Tracker (MantisBT) versions 1.3.0 through 2.28.1, an unescaped Project Name allows an attacker with manager or administrator privileges to inject HTML on the Move Attachments admin page. This vulnerability is fixed in version 2.28.2.
- CVE-2026-40598Medium
Mantis Bug Tracker (MantisBT) versions 2.28.1 and below have a vulnerability due to improper escaping of the redirection page from the Referer header, allowing HTML injection. On specific server configurations, this could lead to cache poisoning and cross-site scripting.
Original NVD description (English source)
Mantis Bug Tracker (MantisBT) is an open source issue tracker. In versions 2.11.0 through 2.28.1, a Stored XSS vulnerability is caused by incorrect escaping of a saved filter's owner, allowing an attacker to inject arbitrary HTML on systems where $g_show_user_realname = ON. Note that By default, only users with Manager access level or above can save their filters publicly. This issue has been fixed in version 2.28.2. If developers are unable to update immediately, they can work around this issue by preventing display of users' real names (set $g_ show_user_realname = OFF; in configuration), and restricting the ability to store filters (set $g_stored_query_create_threshold / $g_stored_query_create_shared_threshold to NOBODY).