CVE-2026-34579
MediumCVSS 5.3Exploitation Probability (EPSS)
Low risk29th percentile - higher than 29% of all known CVEs
Summary
Mantis Bug Tracker (MantisBT) versions 2.28.1 and earlier are vulnerable to authorization bypass via the private issue monitoring feature. A user with project-level access can add themselves as a monitor for a private issue they cannot access by sending a crafted POST request to bug_monitor_add.php. Despite an Access Denied error, the monitor relationship is created, leading to email notifications that disclose private issue metadata and content. This is fixed in version 2.28.2.
Risk Assessment
The risk is that a user with project access can receive notifications about changes in private issues, leading to disclosure of confidential information.
Recommendation
Update MantisBT to version 2.28.2 or later.
Other vulnerabilities in MantisBT
See all- CVE-2014-9624High
CAPTCHA bypass vulnerability in MantisBT before version 1.2.19.
- CVE-2017-7615High
MantisBT through 2.3.0 allows arbitrary password reset and unauthenticated admin access via an empty confirm_hash value to verify.php.
- CVE-2014-9572High
MantisBT before 1.2.19 and 1.3.x before 1.3.0-beta.2 does not properly restrict access to /*/install.php, allowing remote attackers to obtain database credentials via the install parameter with the value 4.
- CVE-2014-9280High
The current_user_get_bug_filter function in core/current_user_api.php in MantisBT before 1.2.18 allows remote attackers to execute arbitrary PHP code via the filter parameter.
- CVE-2014-9089High
Multiple SQL injection vulnerabilities in MantisBT before version 1.2.18 in view_all_bug_page.php allow remote attackers to execute arbitrary SQL commands via the sort or dir parameter to view_all_set.php.
- CVE-2014-8554High
SQL injection vulnerability in the mc_project_get_attachments function in api/soap/mc_project_api.php in MantisBT before 1.2.18 allows remote attackers to execute arbitrary SQL commands via the project_id parameter.
- CVE-2014-1609High
Multiple SQL injection vulnerabilities in MantisBT before version 1.2.16 allow remote attackers to execute arbitrary SQL commands via unspecified parameters in various API functions.
- CVE-2026-47156Critical
MantisBT 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 installations because self-registration is enabled by default.
- CVE-2026-44657High
Mantis Bug Tracker (MantisBT) prior to version 2.28.2 contains a vulnerability that allows code execution by an attacker. By using the show_inline=1 parameter and a valid file_show_inline_token CSRF token on file_download.php, an attacker can upload a crafted XHTML attachment referencing a JavaScript attachment.
- CVE-2026-44655High
In Mantis Bug Tracker (MantisBT) versions 1.3.0 through 2.28.1, an unescaped Project Name allows an attacker with manager or administrator privileges to inject HTML on the Move Attachments admin page. This vulnerability is fixed in version 2.28.2.
Original NVD description (English source)
Mantis Bug Tracker (MantisBT) is an open source issue tracker. Versions 2.28.1 and prior are vulnerable to Authorization Bypass through the private issue monitoring feature . Using a crafted POST request to bug_monitor_add.php, a user with project-level access can add themselves as a monitor for a private issue they do not have access to. Despite displaying an Access Denied error, the application accepts the request and creates a monitor relationship for the private issue. Direct access to the private issue remains blocked, but the user will receive email notifications for updates, leading to disclosure of the private issue's metadata and content. This issue has been fixed in version 2.28.2.
Vulnerability data from NVD (NIST) · CISA KEV · EPSS