# Server-Side Request Forgery in Concrete CMS

Advisory record · `GHSA-mcxr-fx5f-96qq`

- **Identifiers:** `GHSA-mcxr-fx5f-96qq` · `CVE-2021-22969` · `PKSA-hq3g-6kzq-dx63`
- **State:** Confirmed
- **Severity:** No CVSS score
- **Critical:** No
- **Weakness (CWE):** [CWE-918](https://cwe.mitre.org/data/definitions/918.html)
- **Tags:** [Server-side request forgery (SSRF)](https://agentprime.io/advisories/tag/ssrf.md)
- **Published:** 23 Nov 2021
- **Updated:** 2 Dec 2024
- **Reviewed by a person:** No

Published by the GitHub Advisory Database at 23 Nov 2021, 18:18 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

## Affected packages

- `concrete5/core` (Packagist): affected `<8.5.7`; fixed in `8.5.7`

## Machine-written summary

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

> Concrete CMS (concrete5/core) versions below 8.5.7 are vulnerable to a server-side request forgery that bypasses existing mitigations using a DNS rebinding attack. An attacker who can trigger the server to fetch remote resources could use this to retrieve cloud IAM keys from the hosting environment. Upgrade to concrete5/core 8.5.7 or later, which blocks downloads from the local network and fetches the validated IP address instead of re-resolving DNS.

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

No source has published a CVSS score for this record yet.

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

## Timeline

- 31 Oct 2026, 14:28 UTC: First seen by agentprime
- 31 Oct 2026, 14:28 UTC: [Confirmed by OSV](https://osv.dev/vulnerability/GHSA-mcxr-fx5f-96qq)

## Sources

- [GitHub Advisory Database: GHSA-mcxr-fx5f-96qq](https://github.com/advisories/GHSA-mcxr-fx5f-96qq)
- [OSV: GHSA-mcxr-fx5f-96qq](https://osv.dev/vulnerability/GHSA-mcxr-fx5f-96qq)
- <https://nvd.nist.gov/vuln/detail/CVE-2021-22969>
- <https://hackerone.com/reports/1369312>
- <https://documentation.concretecms.org/developers/introduction/version-history/857-release-notes>

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-mcxr-fx5f-96qq>, or `POST https://api.agentprime.io/v1/match` with your packages (<https://agentprime.io/api.md>)

---

The web page: <https://agentprime.io/advisories/GHSA-mcxr-fx5f-96qq/>. Everything for agents: <https://agentprime.io/llms.txt>.
