SEPTEMBER 14, 2026
Live Feed
Back to database
Case File

CVE-2026-47156

CRITICAL · CVSS 9.3 EPSS 0.50% Public Exploit

Source: NVD + CISA KEV + EPSS · Published 2026-09-09 · Last synced 2026-09-14

CyberRota Analysis

AI-Generated

MantisBT versions 2.28.3 and earlier are vulnerable to a critical authentication bypass in the SOAP API, allowing any user with a valid cookie string to impersonate any other user, including administrators, without needing their password. This vulnerability is particularly concerning for default installations where self-registration is enabled, as it can be exploited by any self-registered user. Organizations using MantisBT should prioritize upgrading to version 2.28.4 or later to mitigate this risk, as there are no known workarounds.

Public Exploit Signal

A public exploit, PoC, GitHub repository or Metasploit reference was detected for this CVE.

Detected Signals
exploit

Note: these links are listed for security research and verification purposes only.

CVE
CVE-2026-47156
Severity
CRITICAL
CVSS
9.3
EPSS
0.50%

Original NVD Description

MantisBT is an open source bug tracker. Versions 2.28.3 and earlier contain a critical authentication bypass in the SOAP API's mci_check_login() function. Any user knowing any valid cookie_string can authenticate as any other user (knowing their username), including the administrator, without knowing the target's password. The vulnerability is exploitable with zero prior access on default MantisBT installations because self-registration is enabled by default ($g_allow_signup = ON). A self-registered user can use their own cookie_string (readable from their browser's MANTIS_STRING_COOKIE cookie after login) to impersonate the administrator via the SOAP API. The REST API is NOT affected. The REST API's AuthMiddleware derives the username server-side from the API token or session cookie, so the username cannot be spoofed. The Web UI is NOT affected. The Web UI authenticates via PHP session cookies (PHPSESSID) and validates the MANTIS_STRING_COOKIE against the logged-in user through auth_is_cookie_valid(). The username is derived server-side from the cookie, not supplied by the client. Version 2.28.4 contains a patch. No known workarounds are available.