# GHSA-hhvj-mcrx-3vcf: silverstripe/framework has Cross-site Scripting vulnerability in page name

> An attacker can inject malicious scripts via page names in SilverStripe, potentially stealing user sessions or data.

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

## What is GHSA-hhvj-mcrx-3vcf?

GHSA-hhvj-mcrx-3vcf is a cross-site scripting vulnerability in silverstripe/framework, published on 27 May 2024. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.

### Official description

silverstripe/framework is vulnerable to XSS in Page name where the payload `"><svg/onload=alert(/xss/)>` will trigger an XSS alert.

## Which versions are affected by GHSA-hhvj-mcrx-3vcf?

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


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `silverstripe/framework` | Packagist | From 3.4.0-rc1 | 3.4.4 |
| `silverstripe/framework` | Packagist | From 3.4.0-rc1 | 3.4.4 |
| `silverstripe/framework` | Packagist | From 3.5.0-rc1 | 3.5.2 |
| `silverstripe/framework` | Packagist | From 3.5.0-rc1 | 3.5.2 |

## How do I fix GHSA-hhvj-mcrx-3vcf?

Upgrade silverstripe/framework to a fixed version for your release line: 3.4.4 or 3.5.2.

## Is GHSA-hhvj-mcrx-3vcf being exploited?

There is no known exploitation of GHSA-hhvj-mcrx-3vcf in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for GHSA-hhvj-mcrx-3vcf and fix it if it is affected.

What it is: GHSA-hhvj-mcrx-3vcf is a cross-site scripting vulnerability in silverstripe/framework, published on 27 May 2024. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of GHSA-hhvj-mcrx-3vcf in the wild and no public exploit code.

Affected packages and fixed versions:
- silverstripe/framework (Packagist): affected from 3.4.0-rc1; fixed in 3.4.4
- silverstripe/framework (Packagist): affected from 3.4.0-rc1; fixed in 3.4.4
- silverstripe/framework (Packagist): affected from 3.5.0-rc1; fixed in 3.5.2
- silverstripe/framework (Packagist): affected from 3.5.0-rc1; fixed in 3.5.2

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-hhvj-mcrx-3vcf/ (Markdown: https://insights.sbomify.com/GHSA-hhvj-mcrx-3vcf/index.md)
```

## Sources

- OSV: https://osv.dev/vulnerability/GHSA-hhvj-mcrx-3vcf

---
From sbomify Insights: https://insights.sbomify.com/GHSA-hhvj-mcrx-3vcf/
Summaries are generated and may contain mistakes; the official description above is the record.