GHSA-wjg9-v8cf-f5q2 json
silverstripe/graphql Cross-Site Request Forgery vulnerability
published 2y ago modified last yr.
- cvss
- 7.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
The GraphQL controller lacked any CSRF protection, meaning authenticated users could be forced or tricked into visiting a URL that would send a GET request to the affected web server that could mutate or destroy data without the user knowing.
Patch / fix
Is GHSA-wjg9-v8cf-f5q2 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 | 7.3 | CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:U/C:N/I:H/A:H |
Affected packages
| ecosystem | package | affected | fixed in |
|---|---|---|---|
| packagist | silverstripe/graphql | >=2.0.0, <2.0.3 |
2.0.3 |
Classification
- Weakness
-
- CWE-352 Cross-Site Request Forgery
References
-
github.com
/silverstripe/silverstripe-graphql/commit/b59ba397ff42d8934bd2d9c932514f898c327f64
web
-
github.com
/FriendsOfPHP/security-advisories/blob/master/silverstripe/graphql/SS-2018-007-1.yaml
web
-
github.com
/silverstripe/silverstripe-graphql
package
-
silverstripe.org
/download/security-releases/ss-2018-007
web
Sources
- GitHub Advisory GHSA-wjg9-v8cf-f5q2
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.