External risk intelligence

MantisBT SOAP API Authentication Bypass Vulnerability

CVE advisorySeverity: CRITICAL (CVSS 9.3)

CVE-2026-47156

MantisBT is a bug-tracking web application commonly deployed to be accessible to project teams over the internet. The vulnerability resides in the SOAP API, an interface often exposed by such applications for integration purposes. Because it is a web-based service intended for collaborative access, it frequently sits in an internet-reachable configuration.

Authentication Bypass

Halo Surface Signal: 4 out of 5 — likely to be public-facing.

External exposure likelihood

Horizon Alert

Summary of the vulnerability and why it matters

This advisory concerns a critical vulnerability in the SOAP API of MantisBT, an open-source bug tracking system. The issue allows an attacker to bypass authentication and impersonate any user, including administrators, by leveraging a valid cookie. This could expose sensitive project data and system access.

  • Allows unauthorized user impersonation.
  • Critical for data security and system integrity.
  • Confirm if MantisBT SOAP API is in use.

Attack Path

How an attacker could exploit the issue

An attacker can bypass authentication in MantisBT's SOAP API by knowing a valid user's session cookie and their username. Since self-registration is enabled by default, an attacker can create an account, obtain their own session cookie, and then use it to impersonate any other user, including administrators, without needing their password. This allows the attacker to gain unauthorized access to sensitive information and system functions.

  • Any user with a valid cookie can authenticate.
  • Impersonate any user via the SOAP API.
  • Unauthorized administrative access.

Live Threat

Current exploitation, exposure, and threat context

In default MantisBT installations, a user knowing a valid session cookie string could authenticate as any other user, including an administrator, via the SOAP API. This is possible when self-registration is enabled, allowing a newly registered user to leverage their own cookie to impersonate an administrator.

  • Administrator account access.
  • Cookie theft via browser.
  • Unauthorized administrative actions.

Operational Fix

Recommended remediation, mitigation, and detection steps

Technical leaders and system owners should prioritize identifying all MantisBT installations, particularly those with exposed SOAP APIs and enabled self-registration, as these present the highest risk. Confirming the business criticality and identifying the accountable owner for each instance is crucial before planning remediation.

  • Application or platform owners should manage the issue.
  • Verify SOAP API exposure and self-registration status.
  • Plan remediation during the next maintenance window.

Supplementary metadata

Validate whether this threat affects your internet-facing exposure.

Halo Threat Intelligence helps prioritize remediation with Halo Surface Signal and H/A/L/O context. Start exposure validation with a free external attack surface trial.

Frequently asked questions

What is MantisBT?

MantisBT is an open-source web application designed for tracking software bugs and project tasks. Teams use it to collaborate on development cycles, manage issues, and maintain documentation. Because it is a collaborative platform, it is often installed on web servers where it handles user credentials and project data.

What is the vulnerability in CVE-2026-47156?

This CVE involves improper authentication, specifically classified under CWE-287 and CWE-639. In the SOAP API, the software fails to properly verify the identity of a user. Instead of checking if a user has the right password for an account, the system incorrectly trusts a provided session cookie. This flaw allows someone to log in as anyone else, including an administrator, simply by knowing their username.

How does an attacker trigger this bypass?

An attacker needs a valid session cookie, which they can easily obtain by creating an account on a MantisBT site where self-registration is enabled. By supplying this cookie alongside a target's username to the SOAP API, they can assume that person's identity. Importantly, the Web UI and the REST API are not affected by this bug, as they validate session and user information securely on the server side.

Is my MantisBT instance at risk?

According to Halo Surface Signal, this vulnerability is significant because MantisBT is commonly configured to be accessible over the internet for team collaboration. If your instance runs an affected version and exposes the SOAP API—which is often used for integrations—your system is a prime target for remote attackers seeking unauthorized administrative access.

Do I need to update my MantisBT software?

Yes, you should upgrade to version 2.28.4 or later as soon as possible, as it contains the necessary security patch. Since no other workarounds exist to secure the SOAP API, planning an upgrade during your next maintenance window is the primary way to protect your project data and prevent unauthorized account impersonation.

References