# CVE-2025-47776: MantisBT: Authentication bypass for some passwords due to PHP type juggling

> Attackers can bypass authentication in MantisBT using PHP type juggling if MD5 login is enabled, allowing unauthorized access to user accounts.

- **Severity:** High 8.8 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:L/VI:H/VA:N/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 4 Nov 2025
- **Updated:** 5 Nov 2025
- **Also known as:** GHSA-4v8w-gg5j-ph37

## What is CVE-2025-47776?

CVE-2025-47776 is a high-severity authentication bypass vulnerability in Mantisbt Mantisbt, published on 4 Nov 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

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.

Weakness: CWE-305 (Authentication Bypass by Primary Weakness)

## Which versions are affected by CVE-2025-47776?

2 open source packages ship an affected version, including mantisbt/mantisbt. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `mantisbt/mantisbt` | Packagist | All versions | 2.27.2 |
| `mantisbt/mantisbt` | Packagist | All versions | 2.27.2 |

Products: Mantisbt Mantisbt.

## How do I fix CVE-2025-47776?

Upgrade mantisbt/mantisbt to 2.27.2 or later.

## Is CVE-2025-47776 being exploited?

There is no known exploitation of CVE-2025-47776 in the wild and no public exploit code.

## Other vulnerabilities in Mantisbt Mantisbt

- [CVE-2019-15074](https://insights.sbomify.com/CVE-2019-15074/): MantisBT allows cross-site scripting (XSS) via crafted filename (critical 9.6)
- [CVE-2026-30849](https://insights.sbomify.com/CVE-2026-30849/): MantisBT SOAP API has an authentication bypass vulnerability on MySQL (critical 9.3)
- [CVE-2017-7615](https://insights.sbomify.com/CVE-2017-7615/): MantisBT allows arbitrary password reset (high 8.8)
- [CVE-2026-33517](https://insights.sbomify.com/CVE-2026-33517/): MantisBT Vulnerable to Stored HTML Injection in Tag Delete Confirmation (high 8.6)
- [CVE-2026-33548](https://insights.sbomify.com/CVE-2026-33548/): MantisBT has Stored HTML Injection / XSS when displaying Tags in Timeline (high 8.6)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-47776 and fix it if it is affected.

What it is: CVE-2025-47776 is a high-severity authentication bypass vulnerability in Mantisbt Mantisbt, published on 4 Nov 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2025-47776 in the wild and no public exploit code.

Affected packages and fixed versions:
- mantisbt/mantisbt (Packagist): affected all versions; fixed in 2.27.2
- mantisbt/mantisbt (Packagist): affected all versions; fixed in 2.27.2

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2025-47776/ (Markdown: https://insights.sbomify.com/CVE-2025-47776/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2025-47776
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2025-47776
- OSV: https://osv.dev/vulnerability/CVE-2025-47776

---
From sbomify Insights: https://insights.sbomify.com/CVE-2025-47776/
Summaries are generated and may contain mistakes; the official description above is the record.