MantisBT is vulnerable to authentication bypass through the SOAP API on MySQL

Exploitation

No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.

CVSS 4.0

9.3 · CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:L/SC:N/SI:N/SA:N · score source

EPSS

• CVE-2026-30849: 1.76% estimated exploitation activity in the next 30 days; percentile 78.02 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.

As published by the source; long descriptions are shortened.

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. Resources - https://mantisbt.org/bugs/view.php?id=36902 Credits MantisBT thanks Alexander Philiotis of SynerComm for discovering and responsibly reporting the issue.

Published by the source

23 Mar 2026, 20:28 UTC

Last modified by the source

25 Mar 2026, 20:44 UTC

Source last checked

26 Oct 2026, 14:39 UTC

1. Revision 1 · created · 26 Oct 2026

   Published from ghsa record GHSA-phrq-pc6r-f6gh

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2026-30849

Advisory: MantisBT is vulnerable to authentication bypass through the SOAP API on MySQL
IDs: CVE-2026-30849, GHSA-phrq-pc6r-f6gh
Record: https://patchnext.com/advisories/cve-2026-30849 (revision 1, source checked 26 Oct 2026, 14:39 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Critical (CVSS 9.3)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: mantisbt/mantisbt 2.28.1. A vendor fix does not mean a deployment is fixed.

## Affected components
- Packagist mantisbt/mantisbt: affected < 2.28.1; fixed in 2.28.1

## Suggested inspection (read-only)
- Packagist mantisbt/mantisbt: check the installed version with your package manager.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on mantisbt/mantisbt.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://github.com/advisories/GHSA-phrq-pc6r-f6gh (GitHub-reviewed advisory GHSA-phrq-pc6r-f6gh lists affected ranges: Packagist mantisbt/mantisbt >=0 <2.28.1)

Commands are suggestions: review each one before running it.