Advisory record · GHSA-vj2j-6g3w-4662

Silverstripe Missing CSRF protection in login form

CVSS 5.4 Medium

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.

PackageEcosystemAffectedFixed in
silverstripe/frameworkPackagist>=3.1.18, <3.1.19 || >=3.2.3, <3.2.4 || >=3.3.1, <3.3.23.1.19, 3.2.4, 3.3.2
Identifiers
GHSA-vj2j-6g3w-4662 · PKSA-drtz-1sqz-9xcw
Weakness (CWE)
CWE-352
Published
23 May 2024
Updated
28 Nov 2024

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

ScoreRatingCVSSVectorSource
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

  1. 31 Oct 2026, 14:29 UTC First seen by agentprime
  2. 31 Oct 2026, 14:29 UTC Confirmed by OSV

Sources

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.