# GHSA-5f5v-5c3v-gw5v: Silverstripe IE requests not properly behaving with rewritehashlinks

> Silverstripe CMS allows cross-site scripting via unencoded URL parameters in Internet Explorer requests, enabling attackers to inject malicious JavaScript.

- **Severity:** Not scored
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** Yes
- **Published:** 23 May 2024

## What is GHSA-5f5v-5c3v-gw5v?

GHSA-5f5v-5c3v-gw5v is a cross-site scripting vulnerability in silverstripe/framework, published on 23 May 2024. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

Non IE browsers don’t appear to be affected, but I haven’t tested a wide range of browsers to be sure 

Requests that come through from IE do NOT appear to encode all entities in the URL string, meaning they are inserted into output content directly by SSViewer::process() when rewriting hashlinks, as it directly outputs $_SERVER[‘REQUEST_URI’]

**Example IE8 request**
127.0.0.1 - - [18/Jun/2014:14:13:42 +1000] “GET /site/cars/brands/toyota?one=1\”onmouseover=\”alert(‘things’);\” HTTP/1.1” 200

**Example FF request**
127.0.0.1 - - [18/Jun/2014:14:14:22 +1000] “GET /site/cars/brands/toyota?one=1\%22onmouseover=\%22alert(%27things%27);\%22 HTTP/1.1” 200

This causes any hash anchor to have the JS code inserted into the page as-is.

## Which versions are affected by GHSA-5f5v-5c3v-gw5v?

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


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `silverstripe/framework` | Packagist | All versions | 3.0.13 |
| `silverstripe/framework` | Packagist | All versions | 3.0.13 |
| `silverstripe/framework` | Packagist | From 3.1.0 | 3.1.12 |
| `silverstripe/framework` | Packagist | From 3.1.0 | 3.1.12 |

## How do I fix GHSA-5f5v-5c3v-gw5v?

Upgrade silverstripe/framework to a fixed version for your release line: 3.0.13 or 3.1.12.

## Is GHSA-5f5v-5c3v-gw5v being exploited?

There is no known exploitation of GHSA-5f5v-5c3v-gw5v in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for GHSA-5f5v-5c3v-gw5v and fix it if it is affected.

What it is: GHSA-5f5v-5c3v-gw5v is a cross-site scripting vulnerability in silverstripe/framework, published on 23 May 2024. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of GHSA-5f5v-5c3v-gw5v in the wild and no public exploit code.

Affected packages and fixed versions:
- silverstripe/framework (Packagist): affected all versions; fixed in 3.0.13
- silverstripe/framework (Packagist): affected all versions; fixed in 3.0.13
- silverstripe/framework (Packagist): affected from 3.1.0; fixed in 3.1.12
- silverstripe/framework (Packagist): affected from 3.1.0; fixed in 3.1.12

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-5f5v-5c3v-gw5v/ (Markdown: https://insights.sbomify.com/GHSA-5f5v-5c3v-gw5v/index.md)
```

## Sources

- OSV: https://osv.dev/vulnerability/GHSA-5f5v-5c3v-gw5v

---
From sbomify Insights: https://insights.sbomify.com/GHSA-5f5v-5c3v-gw5v/
Summaries are generated and may contain mistakes; the official description above is the record.