silverstripe/graphql Cross-Site Request Forgery vulnerabilityGHSA-wjg9-v8cf-f5q2
HIGHFix: silverstripe/silverstripe-graphql@b59ba39GHSA-wjg9-v8cf-f5q2 is a high-severity (CVSS 7.3) vulnerability in silverstripe/graphql. A fix is available for silverstripe/graphql — see the affected versions and patch details below.
Real-World Exposure
silverstripe/graphqlReal-time download stats are indexed for npm and PyPI packages. This vulnerability affects Packagist packages — download data is not available via public APIs for these ecosystems.
Description
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.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 🐘Packagist | silverstripe/graphql | ≥ 2.0.0&&< 2.0.3 | 2.0.3composer require silverstripe/graphql:^2.0.3 |
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for silverstripe/graphql, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update silverstripe/graphql to 2.0.3 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-wjg9-v8cf-f5q2 is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
Frequently Asked Questions
Is GHSA-wjg9-v8cf-f5q2 in your dependencies?
Find it across Packagist, including transitive dependencies.