CVE-2019-12437 json
Silverstripe CSRF Protection Bypass via GraphQL
published 2020-02-19 6 y ago modified 2026-06-17 4 mo ago also GHSA-fx37-56v6-85q6 , EUVD-2022-3848
- cvss
- 8.8
- version 3.1, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.7%
- EPSS 0.7% chance of exploitation in 30 days, percentile 54%
- public exploits
- 0
- none known
Summary
In SilverStripe through 4.3.3, the previous fix for SS-2018-007 does not completely mitigate the risk of CSRF in GraphQL mutations,
Patch / fix
- packagist silverstripe/graphql 2.0.5, 3.1.2
Exploit prediction
0.74% chance of exploitation in the next 30 days, higher than 54% of all scored CVEs (FIRST EPSS, 2026-11-08).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 3.1 | 8.8 | CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H |
| NVD | 2.0 | 6.8 | AV:N/AC:M/Au:N/C:P/I:P/A:P |
| GitHub | 3.1 | 8.8 | CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H |
Affected packages
| ecosystem | package | affected | fixed in |
|---|---|---|---|
| packagist | silverstripe/graphql | >=2.0.0, <2.0.5 >=3.1.0, <3.1.2 |
2.0.5 3.1.2 |
Classification
- Weakness
-
- CWE-352 Cross-Site Request Forgery
References
-
github.com
/silverstripe/silverstripe-graphql/commit/3c1dd6b839b7c0e2cbc85074bb5840ebded6097c
web
-
github.com
/silverstripe/silverstripe-graphql/commit/db28f3075ae2335905f43ac808e9177497e354ff
web
-
silverstripe.org
/download/security-releases/
vendor-advisory
-
silverstripe.org
/blog/tag/release
release-notes, vendor-advisory
-
forum.silverstripe.org
/c/releases
release-notes, vendor-advisory
-
nvd.nist.gov
/vuln/detail/CVE-2019-12437
advisory
-
github.com
/FriendsOfPHP/security-advisories/blob/master/silverstripe/graphql/CVE-2019-12437.yaml
web
-
github.com
/silverstripe/silverstripe-graphql
package
-
silverstripe.org
/download/security-releases/cve-2019-12437
web
Sources
- CVE List CVE-2019-12437
- GitHub Advisory GHSA-fx37-56v6-85q6
- NVD CVE-2019-12437
Fencer Vulns 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.