Summary
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.
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.
Resources
Credits
MantisBT thanks Alexander Philiotis of SynerComm for discovering and responsibly reporting the issue.
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.
Affected versions
Security releases
Kodem intelligence
Severity tells you how bad this could be in the worst case. It does not tell you whether you are exposed. Exploitability and impact are functions of runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A vulnerable package can sit in your dependency tree and never run.
Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter. Kodem's runtime-powered SCA identifies whether this CVE is reachable in your applications.
Remediation advice
- b349e5c890eeda9bd82e7c7e14479853f8a30d9f
Frequently Asked Questions
- What is CVE-2026-30849? CVE-2026-30849 is a critical-severity security vulnerability in mantisbt/mantisbt (composer), affecting versions < 2.28.1. It is fixed in 2.28.1.
- Which versions of mantisbt/mantisbt are affected by CVE-2026-30849? mantisbt/mantisbt (composer) versions < 2.28.1 is affected.
- Is there a fix for CVE-2026-30849? Yes. CVE-2026-30849 is fixed in 2.28.1. Upgrade to this version or later.
- Is CVE-2026-30849 exploitable, and should I be worried? Whether CVE-2026-30849 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
- What actually determines whether CVE-2026-30849 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
- How do I fix CVE-2026-30849? Upgrade
mantisbt/mantisbtto 2.28.1 or later.