CVE-2026-47156
CriticalCVSS 9.3Summary
MantisBT versions 2.28.3 and earlier contain a critical authentication bypass in the SOAP API's mci_check_login() function. Any user knowing any valid cookie_string can authenticate as any other user (knowing their username), including the administrator, without knowing the target's password. The vulnerability is exploitable with zero prior access on default installations because self-registration is enabled by default.
Risk Assessment
An attacker can impersonate the administrator and gain full control over the bug tracker, potentially leading to disclosure of sensitive information and data integrity compromise.
Recommendation
Upgrade MantisBT to version 2.28.4 or later, which contains a patch. If not possible, disable self-registration and restrict access to the SOAP API.
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-40607High
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.
Original NVD description (English source)
MantisBT is an open source bug tracker. Versions 2.28.3 and earlier contain a critical authentication bypass in the SOAP API's mci_check_login() function. Any user knowing any valid cookie_string can authenticate as any other user (knowing their username), including the administrator, without knowing the target's password. The vulnerability is exploitable with zero prior access on default MantisBT installations because self-registration is enabled by default ($g_allow_signup = ON). A self-registered user can use their own cookie_string (readable from their browser's MANTIS_STRING_COOKIE cookie after login) to impersonate the administrator via the SOAP API. The REST API is NOT affected. The REST API's AuthMiddleware derives the username server-side from the API token or session cookie, so the username cannot be spoofed. The Web UI is NOT affected. The Web UI authenticates via PHP session cookies (PHPSESSID) and validates the MANTIS_STRING_COOKIE against the logged-in user through auth_is_cookie_valid(). The username is derived server-side from the cookie, not supplied by the client. Version 2.28.4 contains a patch. No known workarounds are available.