High

MantisBT vulnerable to authentication bypass for some passwords due to PHP type juggling

  • Disclosed: 03.11.2025
  • Updated: 11.10.2026 10:22

Due to an incorrect use of loose (==) instead of strict (===) comparison in the authentication code, PHP type juggling will cause interpretation of certain MD5 hashes as numbers, specifically those matching scientific notation.

Impact

On MantisBT instances configured to use the MD5 login method, user accounts having a password hash evaluating to zero (i.e. matching regex ^0+[Ee][0-9]+$) are vulnerable, allowing an attacker knowing the victim's username to login without knowledge of their actual password, using any other password having a hash evaluating to zero, for example comito5 (0e579603064547166083907005281618).

No password bruteforcing for individual users is needed, thus $g_max_failed_login_count does not protect against the attack.

Patches

Workarounds

Check the database for vulnerable accounts, and change those users' passwords, e.g. for MySQL:

sql
SELECT username, email FROM mantis_user_table WHERE password REGEXP '^0+[Ee][0-9]+$'

References

Credits

Thanks to Harry Sintonen / Reversec for discovering and reporting the issue.

Affected software

Click a technology to see all vulnerabilities affecting it.

PlatformPackageVulnerable versionsFixed in
Composer package mantisbt/mantisbt < 2.27.2 2.27.2

References

CVSS score 9.1/10
CVSS vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N
Weakness (CWE)
CWE-305, CWE-697
Platform
Composer
Package
mantisbt/mantisbt
Disclosed
03.11.2025
Updated
11.10.2026 10:22

Sources and licenses

OSV / GitHub Advisory Database - GHSA-4v8w-gg5j-ph37 - CC BY 4.0

Vulnerability history: mantisbt/mantisbt

All published vulnerabilities of this package (Composer package), newest first. Shows whether this is a one-off slip or a package that needs watching.

All (74) in the archive
Total entries
74
First → latest
04.2022 07.2026
Without a fix
2
Exploited in attacks
0

Severity breakdown

  • Critical 4
  • High 20
  • Medium 49
  • Low 1

Disclosures per year

  1. 2022: 34
  2. 2023: 2
  3. 2024: 5
  4. 2025: 4
  5. 2026: 29
Severity:
  1. High CVE-2026-62944 < 2.28.4 2.28.4
  2. Critical CVE-2026-52847 < 2.28.4 2.28.4
  3. High CVE-2026-44657 < 2.28.2 2.28.2
  4. High CVE-2026-44655 >= 1.3.0, < 2.28.2 2.28.2
  5. High CVE-2026-42071 >= 2.23.0, < 2.28.2 2.28.2
  6. High CVE-2026-40607 >= 2.1.0, < 2.28.2 2.28.2
  7. High · 6.1 CVE-2026-33548 >= 2.28.0, < 2.28.2 2.28.2
  8. High CVE-2026-33517 >= 2.28.0, < 2.28.1 2.28.1
  9. MantisBT vulnerable to authentication bypass for some passwords due to PHP type juggling this entry
    High · 9.1 CVE-2025-47776 < 2.27.2 2.27.2
  10. High · 8.3 CVE-2024-23830 < 2.26.1 2.26.1
Show more (4) Showing 20 of 24

Know which vulnerabilities affect your application

With the DockRay integration and software inventory enabled, DockRay checks reported component versions against known vulnerabilities and notifies you about confirmed matches. Coverage depends on the supported technology and available advisory data.

Connect your application
DockRay newsletter

Application security in your inbox

Important vulnerabilities, actionable guidance and practical advice for your applications. Choose your technologies and follow what matters to your project.

  • A daily digest of new vulnerabilities, critical ones included.
  • Notifications about important updates.
  • Practical advice on application security and monitoring.

Leave empty to receive updates for every technology.

Free to subscribe. Unsubscribe with one click in any email.