How severe is CVE-2025-47776?

CVE-2025-47776 has a CVSS 3.x base score of 9.1, rated critical severity. It is exploitable over network with low attack complexity, requires no privileges and no user interaction. Impact on confidentiality is high, integrity high, and availability none.

Is CVE-2025-47776 being actively exploited?

It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 0% (24th percentile), an estimate of the probability of exploitation in the next 30 days.

What products are affected by CVE-2025-47776?

CVE-2025-47776 affects Mantisbt. See the affected-products list for the exact vulnerable versions.

How do I fix CVE-2025-47776?

Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround. Given its critical severity, prioritise patching exposed systems.

Does CVE-2025-47776 have an EU (EUVD) identifier?

Yes. CVE-2025-47776 is tracked in the ENISA EU Vulnerability Database (EUVD) as EUVD-2025-37510.

When was CVE-2025-47776 published?

CVE-2025-47776 was published on 2025-11-04 and last updated on 2026-06-17.

CVE-2025-47776

CVE-2025-47776 is a critical-severity vulnerability in Mantisbt with a CVSS 3.x base score of 9.1. It is not currently listed as actively exploited by CISA, and its EPSS exploit-prediction score is low. The underlying weakness is classified as CWE-305.

Key facts

Severity: Critical (CVSS 3.x base score 9.1)
CVSS v4: 8.8
EPSS exploit prediction: 0% (24th percentile)
Actively exploited: Not listed in CISA KEV
EU (EUVD) id: EUVD-2025-37510
Weakness: CWE-305
Affected product: Mantisbt
Published: 2025-11-04
Last modified: 2026-06-17

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.

Frequently asked questions

What is CVE-2025-47776?: 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.
How severe is CVE-2025-47776?: CVE-2025-47776 has a CVSS 3.x base score of 9.1, rated critical severity. It is exploitable over network with low attack complexity, requires no privileges and no user interaction. Impact on confidentiality is high, integrity high, and availability none.
Is CVE-2025-47776 being actively exploited?: It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 0% (24th percentile), an estimate of the probability of exploitation in the next 30 days.
What products are affected by CVE-2025-47776?: CVE-2025-47776 affects Mantisbt. See the affected-products list for the exact vulnerable versions.
How do I fix CVE-2025-47776?: Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround. Given its critical severity, prioritise patching exposed systems.
Does CVE-2025-47776 have an EU (EUVD) identifier?: Yes. CVE-2025-47776 is tracked in the ENISA EU Vulnerability Database (EUVD) as EUVD-2025-37510.
When was CVE-2025-47776 published?: CVE-2025-47776 was published on 2025-11-04 and last updated on 2026-06-17.

References

Affected products (1)

cpe:2.3:a:mantisbt:mantisbt:*:*:*:*:*:*:*:*

More vulnerabilities in Mantisbt

CVE-2026-30849 — Critical (CVSS 9.8): Mantis Bug Tracker (MantisBT) is an open source issue tracker. Versions prior to 2.28.1 running on MySQL family…
CVE-2019-15074 — Critical (CVSS 9.6): The Timeline feature in my_view_page.php in MantisBT through 2.21.1 has a stored cross-site scripting (XSS)…
CVE-2017-7615 — High (CVSS 8.8): MantisBT through 2.3.0 allows arbitrary password reset and unauthenticated admin access via an empty confirm_hash value…
CVE-2024-23830 — High (CVSS 8.3): MantisBT is an open source issue tracker. Prior to version 2.26.1, an unauthenticated attacker who knows a user's email…
CVE-2009-20001 — High (CVSS 8.1): An issue was discovered in MantisBT before 2.24.5. It associates a unique cookie string with each user. This string is…
CVE-2021-43257 — High (CVSS 7.8): Lack of Neutralization of Formula Elements in the CSV API of MantisBT before 2.25.3 allows an unprivileged attacker to…

All CVEs affecting Mantisbt →

Other CWE-305 vulnerabilities

CVE-2025-4320 — Critical (CVSS 10.0): Authentication Bypass by Primary Weakness, Weak Password Recovery Mechanism for Forgotten Password vulnerability in…
CVE-2025-24522 — Critical (CVSS 10.0): KUNBUS Revolution Pi OS Bookworm 01/2025 is vulnerable because authentication is not configured by default for the…
CVE-2024-36388 — Critical (CVSS 10.0): MileSight DeviceHub - CWE-305 Missing Authentication for Critical Function
CVE-2024-1403 — Critical (CVSS 10.0): In OpenEdge Authentication Gateway and AdminServer prior to 11.7.19, 12.2.14, 12.8.1 on all platforms supported by the…
CVE-2026-25555 — Critical (CVSS 9.8): OpenBullet2 through version 0.3.2 contains an authentication bypass vulnerability in the API key authentication…
CVE-2026-4670 — Critical (CVSS 9.8): Authentication bypass by primary weakness vulnerability in Progress Software MOVEit Automation allows Authentication…

Browse all CWE-305 vulnerabilities →