# GHSA-hq4p-5mpr-jj9m: Silverstripe XSS in dev/build returnURL Parameter

> An XSS vulnerability in the dev/build returnURL parameter allows attackers to redirect users to malicious sites, requiring a framework upgrade.

- **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-hq4p-5mpr-jj9m?

GHSA-hq4p-5mpr-jj9m 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

A XSS risk exists in the returnURL parameter passed to dev/build. An unvalidated url could cause the user to redirect to an unverified third party url outside of the site.

This issue is resolved in framework 3.1.14 stable release.

## Which versions are affected by GHSA-hq4p-5mpr-jj9m?

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


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `silverstripe/framework` | Packagist | All versions | 3.1.14 |
| `silverstripe/framework` | Packagist | All versions | 3.1.14 |

## How do I fix GHSA-hq4p-5mpr-jj9m?

Upgrade silverstripe/framework to 3.1.14 or later.

## Is GHSA-hq4p-5mpr-jj9m being exploited?

There is no known exploitation of GHSA-hq4p-5mpr-jj9m in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for GHSA-hq4p-5mpr-jj9m and fix it if it is affected.

What it is: GHSA-hq4p-5mpr-jj9m 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-hq4p-5mpr-jj9m in the wild and no public exploit code.

Affected packages and fixed versions:
- silverstripe/framework (Packagist): affected all versions; fixed in 3.1.14
- silverstripe/framework (Packagist): affected all versions; fixed in 3.1.14

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-hq4p-5mpr-jj9m/ (Markdown: https://insights.sbomify.com/GHSA-hq4p-5mpr-jj9m/index.md)
```

## Sources

- OSV: https://osv.dev/vulnerability/GHSA-hq4p-5mpr-jj9m

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