# CI4MS: Account Deactivation Module Grants Full Persistent Unauthorized Access for All‑Roles via Improper Session Invalidation (Logic Flaw)

Advisory record · `GHSA-8fq3-c5w3-pj3q`

- **Identifiers:** `GHSA-8fq3-c5w3-pj3q` · `CVE-2026-34572` · `PKSA-srvq-v3bs-mj79`
- **State:** Confirmed
- **Severity:** CVSS 8.8 High
- **Critical:** No
- **Weakness (CWE):** [CWE-284](https://cwe.mitre.org/data/definitions/284.html) · [CWE-613](https://cwe.mitre.org/data/definitions/613.html) · [CWE-1254](https://cwe.mitre.org/data/definitions/1254.html)
- **Tags:** [Broken access control](https://agentprime.io/advisories/tag/access-control.md) · [Authentication bypass](https://agentprime.io/advisories/tag/auth-bypass.md) · [CWE-1254](https://agentprime.io/advisories/tag/cwe-1254.md)
- **Published:** 1 Apr 2026
- **Updated:** 5 May 2026
- **Reviewed by a person:** No

Published by the GitHub Advisory Database at 1 Apr 2026, 22:09 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

## Affected packages

- `ci4-cms-erp/ci4ms` (Packagist): affected `<0.31.0.0`; fixed in `0.31.0.0`

## Machine-written summary

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

> CI4MS (Packagist package ci4-cms-erp/ci4ms) versions before 0.31.0.0 do not end existing sessions when a user account is deactivated, so a deactivated user stays logged in and keeps the access their role allows until they log out. An attacker who already has a valid account and session can exploit this to retain access. Upgrade to version 0.31.0.0 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.8 High, CVSS 3.1: `CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H`, from CNA (GitHub_M)

- **CISA KEV:** Not listed.
- **EPSS:** 0.0051, the 43rd percentile, on 8 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

## Timeline

- 31 Oct 2026, 14:25 UTC: First seen by agentprime
- 31 Oct 2026, 14:25 UTC: [Confirmed by OSV](https://osv.dev/vulnerability/GHSA-8fq3-c5w3-pj3q)

## Sources

- [GitHub Advisory Database: GHSA-8fq3-c5w3-pj3q](https://github.com/advisories/GHSA-8fq3-c5w3-pj3q)
- [OSV: GHSA-8fq3-c5w3-pj3q](https://osv.dev/vulnerability/GHSA-8fq3-c5w3-pj3q)
- <https://github.com/ci4-cms-erp/ci4ms/security/advisories/GHSA-8fq3-c5w3-pj3q>
- <https://nvd.nist.gov/vuln/detail/CVE-2026-34572>
- <https://github.com/ci4-cms-erp/ci4ms>
- <https://github.com/ci4-cms-erp/ci4ms/releases/tag/0.31.0.0>

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-8fq3-c5w3-pj3q>, or `POST https://api.agentprime.io/v1/match` with your packages (<https://agentprime.io/api.md>)

---

The web page: <https://agentprime.io/advisories/GHSA-8fq3-c5w3-pj3q/>. Everything for agents: <https://agentprime.io/llms.txt>.