GHSA-mg2g-8pwj-r2j2
MEDIUMGHSA-mg2g-8pwj-r2j2 is a medium-severity (CVSS 6.5) Improper Authentication vulnerability in silverstripe/graphql. 1 public exploit reference exists, so weaponization risk is real. O3 Security confirms whether GHSA-mg2g-8pwj-r2j2 is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.
Authentication bypass in SilverStripe GraphQL
Blast Radius
silverstripe/graphql🐘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 module accepts basic-auth as an authentication method by default. This can be used to bypass MFA authentication if the silverstripe/mfa module is installed, which is now a commonly installed module. A users password is still required though.
Basic-auth has been removed as a default authentication method. If desired, it can be re-enabled by adding it to the authenticators key of a schema, or on SilverStripe\Graphql\Auth\Handler
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 🐘Packagist | silverstripe/graphql | ≥ 3.0.0&&< 3.5.0 | 3.5.0 |
| 🐘Packagist | silverstripe/graphql | ≥ 4.0.0-alpha1&&< 4.0.0-alpha2 | 4.0.0-alpha2 |
Research use only. For defensive security, authorized penetration testing, and academic research only. Never execute exploit code against systems without explicit written authorization.
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for silverstripe/graphql. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.
Fix
Update silverstripe/graphql to 3.5.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-mg2g-8pwj-r2j2 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.
How O3 protects you
O3 pinpoints whether GHSA-mg2g-8pwj-r2j2 is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.
Tailored to GHSA-mg2g-8pwj-r2j2. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.
Frequently Asked Questions
Is GHSA-mg2g-8pwj-r2j2 in your dependencies?
O3 detects GHSA-mg2g-8pwj-r2j2 across Packagist dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.