CVE-2026-30849: MantisBT is vulnerable to authentication bypass through the SOAP API on MySQL

Should you act?

Critical and remotely reachable

No known exploitation yet, but it is network-reachable without credentials. This signal is computed from CISA KEV, EPSS and CVSS data; it is not an editorial verdict.

• No confirmed exploitation. It is not in CISA’s KEV catalog and CISA’s SSVC assessment records no known exploitation. That can change quickly after a public write-up; re-check if you are affected.
• EPSS 2.4%, percentile 84: FIRST’s model estimates a 2.4% chance of exploitation activity in the next 30 days, higher than 84% of all scored CVEs (elevated). EPSS is a probability, not a verdict.
• Remotely reachable with no login and no user interaction. If the vulnerable service is exposed to the internet, prioritize it.
• Only applies if your dependency tree includes mantisbt/mantisbt (Composer (PHP)) < 2.28.1, fixed in 2.28.1. Check your lockfile, including transitive dependencies.

What it is

Mantis Bug Tracker (MantisBT) is an open source issue tracker. Versions prior to 2.28.1 running on MySQL family databases are affected by an authentication bypass vulnerability in the SOAP API, as a result of an improper type checking on the password parameter. Other database backends are not affected, as they do not perform implicit type conversion from string to integer. Using a crafted SOAP envelope, an attacker knowing the victim's username is able to login to the SOAP API with their account without knowledge of the actual password, and execute any API function they have access to. Version 2.28.1 contains a patch. Disabling the SOAP API significantly reduces the risk, but still allows the attacker to retrieve user account information including email address and real name.

From the GitHub advisory

Mantis Bug Tracker instances running on MySQL and compatible databases are affected by an authentication bypass vulnerability in the SOAP API, as a result of improper type checking on the password parameter.

Other database backends are not affected, as they do not perform implicit type conversion from string to integer.

Impact Using a crafted SOAP envelope, an attacker knowing the victim's username is able to login to the SOAP API with their account without knowledge of the actual password, and execute any API function they have access to.

Patches b349e5c890eeda9bd82e7c7e14479853f8a30d9f

Workarounds - Disabling the SOAP API significantly reduces the risk, but still allows the attacker to retrieve user account information including email address and real name.

Weakness type: CWE-305.

Product: mantisbt/mantisbt (Composer (PHP)) · Assigned by: GitHub_M · Published: 2026-03-23

Affected and fixed versions

Severity scores

• Attack vector: network (remotely reachable)
• Attack complexity: low
• Attack requirements: none
• Privileges required: none (no login)
• User interaction: none

CVSS measures how bad a flaw is if exploited, not how likely exploitation is. Read it next to the exploitation data below.

Exploitation and urgency

• CISA KEV: not listed (no confirmed in-the-wild exploitation known to CISA).
• CISA SSVC assessment: exploitation none, automatable yes, technical impact total.
• FIRST EPSS (model of 2026-10-21): 2.35% probability of exploitation activity in the next 30 days; percentile 84.

Timeline

• 2026-03-23 — CVE record published by GitHub_M
• 2026-03-23 — GitHub-reviewed advisory GHSA-phrq-pc6r-f6gh published (critical)
• 2026-03-24 — CVE record last updated

Sources and references

Original sources first. Version and fix details should always be confirmed against the vendor or project advisory.

Vulnerability records

1. GitHub Advisory GHSA-phrq-pc6r-f6gh github.com
2. CVE.org record CVE-2026-30849 cve.org
3. NVD entry CVE-2026-30849 nvd.nist.gov

Other references from the CVE record and advisory

1. github.com github.com
2. github.com github.com

Critical Composer (PHP) advisories · Today’s Security Digest