CVE-2025-47776
CriticalCVSS 9.1Exploitation Probability (EPSS)
Low risk26th percentile - higher than 26% of all known CVEs
Summary
Mantis Bug Tracker (MantisBT) versions 2.27.1 and below use loose (==) instead of strict (===) comparison in authentication code. PHP type juggling causes certain MD5 hashes matching scientific notation to be interpreted as numbers. Instances using MD5 login allow an attacker who knows the victim's username and has access to an account with a password hash evaluating to zero to log in without knowing the victim's password, using any other password with a hash also evaluating to zero. Fixed in 2.27.2.
Risk Assessment
An attacker can take over a user account without knowing the password if conditions are met. This leads to unauthorized access to the issue tracker and potential information leakage.
Recommendation
Upgrade MantisBT to version 2.27.2 or later. Consider switching from MD5 to a stronger login method.
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-47156Critical
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.
- 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.
Original NVD description (English source)
Mantis Bug Tracker (MantisBT) is an open source issue tracker. Due to incorrect use of loose (==) instead of strict (===) comparison in the authentication code in versions 2.27.1 and below.PHP type juggling will cause certain MD5 hashes matching scientific notation to be interpreted as numbers. Instances using the MD5 login method allow an attacker who knows the victim's username and has access to an account with a password hash that evaluates to zero to log in without knowing the victim's actual password, by using any other password with a hash that also evaluates to zero This issue is fixed in version 2.27.2.
Vulnerability data from NVD (NIST) · CISA KEV · EPSS