# MantisBT has an authorization bypass in private issue monitoring

Advisory record · `GHSA-ggw7-9675-6v4v`

- **Identifiers:** `GHSA-ggw7-9675-6v4v` · `CVE-2026-34579` · `PKSA-wqq3-5hnc-g52v`
- **State:** Confirmed
- **Severity:** CVSS 5.3 Medium
- **Critical:** No
- **Weakness (CWE):** [CWE-200](https://cwe.mitre.org/data/definitions/200.html) · [CWE-201](https://cwe.mitre.org/data/definitions/201.html) · [CWE-863](https://cwe.mitre.org/data/definitions/863.html)
- **Tags:** [Information disclosure](https://agentprime.io/advisories/tag/info-disclosure.md) · [Broken access control](https://agentprime.io/advisories/tag/access-control.md)
- **Published:** 11 May 2026
- **Updated:** 10 Sept 2026
- **Reviewed by a person:** No

Published by the GitHub Advisory Database at 11 May 2026, 19:32 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

## Affected packages

- `mantisbt/mantisbt` (Packagist): affected `>=2.26.1, <2.28.2`; fixed in `2.28.2`

## Machine-written summary

Summary written by Claude Haiku from the source advisory. Not reviewed by a person.

> Versions 2.26.1 up to but not including 2.28.2 of the Packagist package mantisbt/mantisbt are affected. A user who already has project-level access can send a specially crafted POST request to the bug monitoring script and add themselves as a monitor on a private issue they cannot otherwise view, so they receive email notifications that can expose the issue's metadata and content. Upgrade to version 2.28.2, which contains the fix; the source lists no workarounds.

Written 31 Oct 2026.

## Not analysed yet

We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check.

## Severity and exploitation

- 5.3 Medium, CVSS 4.0: `CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N`, from CNA (GitHub_M)

- **CISA KEV:** Not listed.
- **EPSS:** 0.0036, the 30th percentile, on 16 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

## Timeline

- 31 Oct 2026, 13:58 UTC: First seen by agentprime
- 31 Oct 2026, 13:58 UTC: [Confirmed by OSV](https://osv.dev/vulnerability/GHSA-ggw7-9675-6v4v)

## Sources

- [GitHub Advisory Database: GHSA-ggw7-9675-6v4v](https://github.com/advisories/GHSA-ggw7-9675-6v4v)
- [OSV: GHSA-ggw7-9675-6v4v](https://osv.dev/vulnerability/GHSA-ggw7-9675-6v4v)
- <https://github.com/mantisbt/mantisbt/security/advisories/GHSA-ggw7-9675-6v4v>
- <https://nvd.nist.gov/vuln/detail/CVE-2026-34579>
- <https://github.com/mantisbt/mantisbt/commit/0a93267deba445fb9d15250c16e6fdb1246ffa65>
- <https://github.com/mantisbt/mantisbt>
- <https://mantisbt.org/bugs/view.php?id=36975>

Facts on this page come from the GitHub Advisory Database (CC-BY 4.0), OSV and the other sources listed, as published. We don’t reproduce full advisory descriptions, which can contain exploit code.

## Check whether this affects you

A Match means an installed version is in the affected range above. Most don’t affect the app; agentprime hasn’t analysed this one yet.

- With the agentprime MCP server (<https://api.agentprime.io/mcp>), ask your agent to check the project: `check_lockfile` sends a lockfile, `check_packages` a list of installed packages, and both return the Matches and the upgrades that clear them. `get_advisory` returns this record. Setup: <https://agentprime.io/mcp.md>
- In a browser: <https://agentprime.io/check/> reads your lockfile in the browser, never uploading it.
- Whether it touches your code, with file and line: the Claude Code plugin, <https://agentprime.io/plugin.md>
- As JSON: <https://api.agentprime.io/v1/advisories/GHSA-ggw7-9675-6v4v>, or `POST https://api.agentprime.io/v1/match` with your packages (<https://agentprime.io/api.md>)

---

The web page: <https://agentprime.io/advisories/GHSA-ggw7-9675-6v4v/>. Everything for agents: <https://agentprime.io/llms.txt>.
