GHSA-2hpc-mf4q-j885 json
Silverstripe CSRF vulnerability in GridFieldAddExistingAutocompleter
published 2y ago modified last yr.
- cvss
- 4.3
- version 3.1, GitHub
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- —
- no score, EPSS covers CVEs only
- public exploits
- 0
- none known
Summary
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.
Patch / fix
- packagist silverstripe/framework 3.1.17, 3.2.2, 3.3.0
Is GHSA-2hpc-mf4q-j885 in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerCVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| GitHub | 3.1 | 4.3 | CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:L/A:N |
Affected packages
| ecosystem | package | affected | fixed in |
|---|---|---|---|
| packagist | silverstripe/framework | <3.1.17 >=3.2.0, <3.2.2 >=3.3.0-beta1, <3.3.0 |
3.1.17 3.2.2 3.3.0 |
Classification
- Weakness
-
- CWE-352 Cross-Site Request Forgery
References
-
github.com
/silverstripe/silverstripe-framework/commit/013524af5069bb0cf909853f04418d9bef56d18c
web
-
github.com
/silverstripe/silverstripe-framework/commit/56e92f5a32e45849cc9361c8603c31d7010c9d36
web
-
github.com
/silverstripe/silverstripe-framework/commit/e2c77c5a8f13e901c51a3684210811559b592f0c
web
-
github.com
/FriendsOfPHP/security-advisories/blob/master/silverstripe/framework/SS-2016-002-1.yaml
web
-
github.com
/silverstripe/silverstripe-framework
package
-
silverstripe.org
/download/security-releases/ss-2016-002
web
Sources
- GitHub Advisory GHSA-2hpc-mf4q-j885
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.