# Silverstripe Missing CSRF protection in login form

Advisory record · `GHSA-vj2j-6g3w-4662`

- **Identifiers:** `GHSA-vj2j-6g3w-4662` · `PKSA-drtz-1sqz-9xcw`
- **State:** Confirmed
- **Severity:** CVSS 5.4 Medium
- **Critical:** No
- **Weakness (CWE):** [CWE-352](https://cwe.mitre.org/data/definitions/352.html)
- **Tags:** [Cross-site request forgery (CSRF)](https://agentprime.io/advisories/tag/csrf.md)
- **Published:** 23 May 2024
- **Updated:** 28 Nov 2024
- **Reviewed by a person:** No

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

## Affected packages

- `silverstripe/framework` (Packagist): affected `>=3.1.18, <3.1.19 || >=3.2.3, <3.2.4 || >=3.3.1, <3.3.2`; fixed in `3.1.19`, `3.2.4`, `3.3.2`

## Machine-written summary

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

> Silverstripe framework versions 3.1.18 to before 3.1.19, 3.2.3 to before 3.2.4, and 3.3.1 to before 3.3.2 are affected. The login form disables its security token, which leaves it without cross-site request forgery protection; the source gives few details on how this would be exploited. Upgrade silverstripe/framework to 3.1.19, 3.2.4, or 3.3.2, depending on your release line.

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

- 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:** No score.

## Timeline

- 31 Oct 2026, 14:29 UTC: First seen by agentprime
- 31 Oct 2026, 14:29 UTC: [Confirmed by OSV](https://osv.dev/vulnerability/GHSA-vj2j-6g3w-4662)

## Sources

- [GitHub Advisory Database: GHSA-vj2j-6g3w-4662](https://github.com/advisories/GHSA-vj2j-6g3w-4662)
- [OSV: GHSA-vj2j-6g3w-4662](https://osv.dev/vulnerability/GHSA-vj2j-6g3w-4662)
- <https://github.com/silverstripe/silverstripe-framework/commit/a6bd22ab2f3b11a054d20be13306a19089510989>
- <https://github.com/FriendsOfPHP/security-advisories/blob/master/silverstripe/framework/SS-2016-006-1.yaml>
- <https://github.com/silverstripe/silverstripe-framework>
- <https://stackoverflow.com/questions/6412813/do-login-forms-need-tokens-against-csrf-attacks/15350123#15350123>
- <https://www.silverstripe.org/download/security-releases/ss-2016-006>

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-vj2j-6g3w-4662>, or `POST https://api.agentprime.io/v1/match` with your packages (<https://agentprime.io/api.md>)

---

The web page: <https://agentprime.io/advisories/GHSA-vj2j-6g3w-4662/>. Everything for agents: <https://agentprime.io/llms.txt>.
