# Concrete CMS vulnerable to Session Fixation

Advisory record · `GHSA-m53v-5x5x-5m2p`

- **Identifiers:** `GHSA-m53v-5x5x-5m2p` · `CVE-2022-43687` · `PKSA-6whh-xycm-8tys`
- **State:** Confirmed
- **Severity:** CVSS 5.4 Medium
- **Critical:** No
- **Weakness (CWE):** [CWE-384](https://cwe.mitre.org/data/definitions/384.html)
- **Tags:** [Authentication bypass](https://agentprime.io/advisories/tag/auth-bypass.md)
- **Published:** 15 Nov 2022
- **Updated:** 8 Nov 2023
- **Reviewed by a person:** No

Published by the GitHub Advisory Database at 15 Nov 2022, 12:00 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

## Affected packages

- `concrete5/concrete5` (Packagist): affected `<8.5.10 || >=9.0.0, <9.1.3`; fixed in `8.5.10`, `9.1.3`

## Machine-written summary

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

> Concrete CMS (concrete5) versions below 8.5.10 and from 9.0.0 through 9.1.2 are vulnerable to session fixation: the application does not issue a new session ID after successful OAuth authentication. An attacker who can get a victim to use a session identifier the attacker knows may be able to take over that session after login. Upgrade to concrete5 8.5.10 or 9.1.3, or later.

Written 5 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

- 5.4 Medium, CVSS 3.1: `CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:L/I:L/A:N`, from GitHub Advisory Database

- **CISA KEV:** Not listed.
- **EPSS:** 0.0088, 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:32 UTC: First seen by agentprime
- 31 Oct 2026, 14:32 UTC: [Confirmed by OSV](https://osv.dev/vulnerability/GHSA-m53v-5x5x-5m2p)

## Sources

- [GitHub Advisory Database: GHSA-m53v-5x5x-5m2p](https://github.com/advisories/GHSA-m53v-5x5x-5m2p)
- [OSV: GHSA-m53v-5x5x-5m2p](https://osv.dev/vulnerability/GHSA-m53v-5x5x-5m2p)
- <https://nvd.nist.gov/vuln/detail/CVE-2022-43687>
- <https://documentation.concretecms.org/developers/introduction/version-history/8510-release-notes>
- <https://documentation.concretecms.org/developers/introduction/version-history/913-release-notes>
- <https://github.com/concretecms/concretecms>
- <https://github.com/concretecms/concretecms/releases/8.5.10>
- <https://github.com/concretecms/concretecms/releases/9.1.3>
- <https://www.concretecms.org/about/project-news/security/concrete-cms-security-advisory-2022-10-31>

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-m53v-5x5x-5m2p>, or `POST https://api.agentprime.io/v1/match` with your packages (<https://agentprime.io/api.md>)

---

The web page: <https://agentprime.io/advisories/GHSA-m53v-5x5x-5m2p/>. Everything for agents: <https://agentprime.io/llms.txt>.
