# MantisBT Insufficient Session Expiration cookie string not reset after logout

Advisory record · `GHSA-jm72-67rm-763j`

- **Identifiers:** `GHSA-jm72-67rm-763j` · `CVE-2009-20001` · `PKSA-45gx-2q1r-69kb`
- **State:** Confirmed
- **Severity:** CVSS 8.1 High
- **Critical:** No
- **Weakness (CWE):** [CWE-613](https://cwe.mitre.org/data/definitions/613.html)
- **Tags:** [Authentication bypass](https://agentprime.io/advisories/tag/auth-bypass.md)
- **Published:** 21 Apr 2022
- **Updated:** 9 Jun 2025
- **Reviewed by a person:** No

Published by the GitHub Advisory Database at 21 Apr 2022, 01:54 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

## Affected packages

- `mantisbt/mantisbt` (Packagist): affected `<2.24.5`; fixed in `2.24.5`

## Machine-written summary

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

> MantisBT versions before 2.24.5 do not reset a user's session cookie string at logout, so the session remains valid after the user logs out. An attacker who obtains a user's cookie can log in as that user. Upgrade mantisbt/mantisbt to version 2.24.5 or later.

Written 3 Nov 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

- 8.1 High, CVSS 3.1: `CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N`, from GitHub Advisory Database

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

## Timeline

- 31 Oct 2026, 14:27 UTC: First seen by agentprime
- 31 Oct 2026, 14:27 UTC: [Confirmed by OSV](https://osv.dev/vulnerability/GHSA-jm72-67rm-763j)

## Sources

- [GitHub Advisory Database: GHSA-jm72-67rm-763j](https://github.com/advisories/GHSA-jm72-67rm-763j)
- [OSV: GHSA-jm72-67rm-763j](https://osv.dev/vulnerability/GHSA-jm72-67rm-763j)
- <https://nvd.nist.gov/vuln/detail/CVE-2009-20001>
- <https://github.com/mantisbt/mantisbt/commit/79a78c09d5ef5ce098adc73f6f1416f00fc238a5>
- <https://github.com/mantisbt/mantisbt>
- <https://mantisbt.org/bugs/view.php?id=11296>
- <https://mantisbt.org/bugs/view.php?id=27976>

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-jm72-67rm-763j>, or `POST https://api.agentprime.io/v1/match` with your packages (<https://agentprime.io/api.md>)

---

The web page: <https://agentprime.io/advisories/GHSA-jm72-67rm-763j/>. Everything for agents: <https://agentprime.io/llms.txt>.
