# GHSA-55qg-6c4m-mw6g: silverstripe/framework's URL parameters `isDev` and `isTest` unguarded

> Unauthenticated attackers can enable debug mode via URL parameters to expose verbose errors and backtraces, potentially leaking sensitive system information.

- **Severity:** Not scored
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 27 May 2024

## What is GHSA-55qg-6c4m-mw6g?

GHSA-55qg-6c4m-mw6g is a vulnerability in silverstripe/framework, published on 27 May 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The URL parameters `isDev` and `isTest` are accessible to unauthenticated users who access a SilverStripe website or application. This allows unauthorised users to expose information that is usually hidden on production environments such as verbose errors (including backtraces) and other debugging tools only available to sites running in "dev mode". Core functionality does not expose user data through these methods. Depending on your website configuration, community modules might have added more specific functionality which can be used to either access or alter user data.

We have fixed the usage of isDev and isTest in SilverStripe 4.x, and removed the URL parameters in the next major release of SilverStripe.

## Which versions are affected by GHSA-55qg-6c4m-mw6g?

4 open source packages ship an affected version, including silverstripe/framework.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `silverstripe/framework` | Packagist | From 4.0.0-rc1 | 4.0.4 |
| `silverstripe/framework` | Packagist | From 4.0.0-rc1 | 4.0.4 |
| `silverstripe/framework` | Packagist | From 4.1.0rc1 | 4.1.1 |
| `silverstripe/framework` | Packagist | From 4.1.0rc1 | 4.1.1 |

## How do I fix GHSA-55qg-6c4m-mw6g?

Upgrade silverstripe/framework to a fixed version for your release line: 4.0.4 or 4.1.1.

## Is GHSA-55qg-6c4m-mw6g being exploited?

There is no known exploitation of GHSA-55qg-6c4m-mw6g in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for GHSA-55qg-6c4m-mw6g and fix it if it is affected.

What it is: GHSA-55qg-6c4m-mw6g is a vulnerability in silverstripe/framework, published on 27 May 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of GHSA-55qg-6c4m-mw6g in the wild and no public exploit code.

Affected packages and fixed versions:
- silverstripe/framework (Packagist): affected from 4.0.0-rc1; fixed in 4.0.4
- silverstripe/framework (Packagist): affected from 4.0.0-rc1; fixed in 4.0.4
- silverstripe/framework (Packagist): affected from 4.1.0rc1; fixed in 4.1.1
- silverstripe/framework (Packagist): affected from 4.1.0rc1; fixed in 4.1.1

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/GHSA-55qg-6c4m-mw6g/ (Markdown: https://insights.sbomify.com/GHSA-55qg-6c4m-mw6g/index.md)
```

## Sources

- OSV: https://osv.dev/vulnerability/GHSA-55qg-6c4m-mw6g

---
From sbomify Insights: https://insights.sbomify.com/GHSA-55qg-6c4m-mw6g/
Summaries are generated and may contain mistakes; the official description above is the record.