MantisBT has an authorization bypass in private issue monitoring
Impact
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.
Source excerpt · OSVAffected packages
Start with the recorded fix for your release branch. Check your installed version and test compatibility before upgrading. Fixing this advisory does not rule out other vulnerabilities in the release.
| Affected range | Recorded fix |
|---|---|
| From 2.26.1 before 2.28.2Ecosystem versions | 2.28.2 |
Version evidence: OSV · GHSA-ggw7-9675-6v4v
View original version evidence (10 explicit versions)
Original source description
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.
Impact
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.
Patches
- 0a93267deba445fb9d15250c16e6fdb1246ffa65
Workarounds
None
Credits
Thanks to Vishal Shukla for discovering and responsibly reporting the issue.
References
- Security advisory github.com/mantisbt/mantisbt/security/advisories/GHSA-ggw7-9675-6v4v
- Security advisory nvd.nist.gov/vuln/detail/CVE-2026-34579
- Patch github.com/mantisbt/mantisbt/commit/0a93267deba445fb9d15250c16e6fdb1246ffa65
- Source reference github.com/mantisbt/mantisbt
- Source reference mantisbt.org/bugs/view.php