Summary
SilverStripe Vulnerability on 'isDev', 'isTest' and 'flush' $_GET validation
When a secure token parameter is provided to a SilverStripe site (such as isDev or flush) an empty token parameter can be provided in order to bypass normal authentication parameters.
For instance, http://www.mysite.com/?isDev=1&isDevtoken will force a site to dev mode. Alternatively, "flush" could also be used in succession to cause excessive load on a victim site and risk denial of service.
The fix in this case is to ensure that empty tokens fail the validation check.
Impact
GHSA-G4HP-PFVF-VM5W has a CVSS score of 6.5 (Medium). The vector is network-reachable, no privileges required, and no user interaction. A CVSS score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether this affects your application depends on whether the vulnerable code is present and reachable in your environment. A fixed version is available (3.0.14, 3.1.13); upgrading removes the vulnerable code path.
Affected versions
Security releases
Kodem intelligence
Severity tells you how bad this could be in the worst case. It does not tell you whether you are exposed. Exploitability and impact are functions of runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A vulnerable package can sit in your dependency tree and never run.
Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter. Kodem's runtime-powered SCA identifies whether this CVE is reachable in your applications.
Already deployed Kodem?
See it in your environmentNew to Kodem? Get a demo →Remediation advice
silverstripe/framework to 3.0.14 or later; silverstripe/framework to 3.1.13 or later
Kodem Kai can prioritize this vulnerability in your dependency tree and generate a fix recommendation.
Frequently Asked Questions
- What is GHSA-G4HP-PFVF-VM5W? GHSA-G4HP-PFVF-VM5W is a medium-severity security vulnerability in silverstripe/framework (composer), affecting versions >= 3.0.0, <= 3.0.13. It is fixed in 3.0.14, 3.1.13.
- How severe is GHSA-G4HP-PFVF-VM5W? GHSA-G4HP-PFVF-VM5W has a CVSS score of 6.5 (Medium). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.
- Which versions of silverstripe/framework are affected by GHSA-G4HP-PFVF-VM5W? silverstripe/framework (composer) versions >= 3.0.0, <= 3.0.13 is affected.
- Is there a fix for GHSA-G4HP-PFVF-VM5W? Yes. GHSA-G4HP-PFVF-VM5W is fixed in 3.0.14, 3.1.13. Upgrade to this version or later.
- Is GHSA-G4HP-PFVF-VM5W exploitable, and should I be worried? Whether GHSA-G4HP-PFVF-VM5W is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
- What actually determines whether GHSA-G4HP-PFVF-VM5W is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
- How do I fix GHSA-G4HP-PFVF-VM5W?
- Upgrade
silverstripe/frameworkto 3.0.14 or later - Upgrade
silverstripe/frameworkto 3.1.13 or later
- Upgrade