dbcve.org
MantisbtApplication

CVE-2026-30849

CRITICAL · 9.8 CVSS v3.1 Published 2026-03-23
Fix available
A fix is available. Upgrade to 2.28.1 or later.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click Patch available

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

MantisBT versions prior to 2.28.1 running on MySQL family databases contain an authentication bypass in the SOAP API due to improper type checking on the password parameter. MySQL performs implicit type conversion from string to integer, allowing attackers with knowledge of a victim's username to bypass authentication using a crafted SOAP envelope and execute any API functions the account can access.

MitigationUpgrade MantisBT to version 2.28.1 or later to apply the patch. As a compensating control, disable the SOAP API if not required, though this still allows enumeration of user email addresses and real names.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
MantisbtApplication
Affected:< 2.28.1

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Check MantisBT version
    Log in as administrator and navigate to 'Manage' > 'Manage Configuration' > 'System Info', or inspect the version field in the MantisBT installation (typically shown on the admin login page or in a version file within the installation directory)
    Affected if The displayed version number is less than 2.28.1 (for example, 2.28.0, 2.27.0, 2.26.0, etc.)
  2. Confirm database type
    Locate the MantisBT configuration file (config/config_inc.php) and check the $g_db_type setting, or in the MantisBT admin area under 'Manage' > 'Manage Configuration' > 'Database' check the database type in use
    Affected if The database type is set to 'MySQL' (or 'mysqli')
  3. Verify SOAP API is enabled
    In the MantisBT admin area, go to 'Manage' > 'Manage Configuration' > 'API' and check if SOAP API is enabled, or inspect the configuration file for $g_webservice_soap_enabled = ON;
    Affected if The SOAP API functionality is enabled in the MantisBT configuration

A user is affected if their MantisBT installation is version 2.28.0 or earlier, uses MySQL as the database, and has the SOAP API enabled, allowing a numeric username in a SOAP request to bypass password verification.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 2.28.1 or later
Fixed in 2.28.1
Vendor patch github.com →
Interim mitigation

Upgrade MantisBT to version 2.28.1 or later to apply the patch. As a compensating control, disable the SOAP API if not required, though this still allows enumeration of user email addresses and real names.

Recommended fix High confidence

2.28.1

  1. Download MantisBT version 2.28.1 or later from the official repository
  2. Backup your existing MantisBT installation and database
  3. Replace the existing MantisBT files with the new version files
  4. Run any database upgrades if required (access /admin/install.php or follow upgrade instructions)
  5. Verify the fix by checking that the password parameter in the SOAP API now performs proper type validation
  6. Optionally disable the SOAP API if not required by setting $g_enable_webservices = OFF; in config.php
Caveat Point release upgrade typically has minimal breaking changes; review release notes for any configuration changes

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Mantisbt Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing4.0 h
  • Review / QA2.0 h
12.0 hours of engineering $2,080
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,328.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-30849 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-30849 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data