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.
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
| Score | Rating | CVSS | Vector | Source |
|---|---|---|---|---|
| 5.4 | Medium | 3.1 | CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:L/I:L/A:N | 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
Sources
- GitHub Advisory Database: GHSA-vj2j-6g3w-4662
- OSV: GHSA-vj2j-6g3w-4662
- github.com/silverstripe/silverstripe-framework/commit/a6bd22ab2f3b11a054d20be13306a19089510989
- github.com/FriendsOfPHP/security-advisories/blob/master/silverstripe/framework/SS-2016-006-1.yaml
- github.com/silverstripe/silverstripe-framework
- stackoverflow.com/questions/6412813/do-login-forms-need-tokens-against-csrf-attacks/15350123#15350123
- www.silverstripe.org/download/security-releases/ss-2016-006