Silverstripe CSRF vulnerability in GridFieldAddExistingAutocompleter
Impact
GridField does not have sufficient CSRF protection, meaning that in some cases users with CMS access can be tricked into posting unspecified data into the CMS from external websites. Amongst other default CMS interfaces, GridField is used for management of groups, users and permissions in the CMS.
Source excerpt · OSVAffected packages
Start with the recorded fix for your release branch. Check your installed version and test compatibility before upgrading. Fixing this advisory does not rule out other vulnerabilities in the release.
| Affected range | Recorded fix |
|---|---|
| Earlier releases before 3.1.17Ecosystem versions | 3.1.17 |
| From 3.2.0 before 3.2.2Ecosystem versions | 3.2.2 |
| From 3.3.0-beta1 before 3.3.0Ecosystem versions | 3.3.0 |
Version evidence: OSV · GHSA-2hpc-mf4q-j885
View original version evidence (78 explicit versions)
Original source description
GridField does not have sufficient CSRF protection, meaning that in some cases users with CMS access can be tricked into posting unspecified data into the CMS from external websites. Amongst other default CMS interfaces, GridField is used for management of groups, users and permissions in the CMS.
The resolution for this issue is to ensure that all gridFieldAlterAction submissions are checked for the SecurityID token during submission.
References
- Patch github.com/silverstripe/silverstripe-framework/commit/013524af5069bb0cf909853f04418d9bef56d18c
- Patch github.com/silverstripe/silverstripe-framework/commit/56e92f5a32e45849cc9361c8603c31d7010c9d36
- Patch github.com/silverstripe/silverstripe-framework/commit/e2c77c5a8f13e901c51a3684210811559b592f0c
- Security advisory github.com/FriendsOfPHP/security-advisories/blob/master/silverstripe/framework/SS-2016-002-1.yaml
- Source reference github.com/silverstripe/silverstripe-framework
- Security advisory www.silverstripe.org/download/security-releases/ss-2016-002