# GHSA-r97r-64vp-fghm: Silverstripe XSS vulnerability via VirtualPage

> An attacker with CMS access can inject malicious HTML into VirtualPage fields, leading to cross-site scripting attacks against other users.

- **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:** 22 May 2024

## What is GHSA-r97r-64vp-fghm?

GHSA-r97r-64vp-fghm is a cross-site scripting vulnerability in silverstripe/cms, published on 22 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

A cross-site scripting vulnerability has been discovered in the VirtualPage class.

This vulnerability can only be exploited if a user with CMS access has posted malicious or unescaped HTML into any of the textfields of a page which a VirtualPage refers to.

This has been resolved by ensuring that VirtualPage safely escapes all field content.

## Which versions are affected by GHSA-r97r-64vp-fghm?

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


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `silverstripe/cms` | Packagist | From 3.1.0 | 3.1.10 |
| `silverstripe/cms` | Packagist | From 3.1.0 | 3.1.10 |

## How do I fix GHSA-r97r-64vp-fghm?

Upgrade silverstripe/cms to 3.1.10 or later.

## Is GHSA-r97r-64vp-fghm being exploited?

There is no known exploitation of GHSA-r97r-64vp-fghm in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for GHSA-r97r-64vp-fghm and fix it if it is affected.

What it is: GHSA-r97r-64vp-fghm is a cross-site scripting vulnerability in silverstripe/cms, published on 22 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-r97r-64vp-fghm in the wild and no public exploit code.

Affected packages and fixed versions:
- silverstripe/cms (Packagist): affected from 3.1.0; fixed in 3.1.10
- silverstripe/cms (Packagist): affected from 3.1.0; fixed in 3.1.10

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-r97r-64vp-fghm/ (Markdown: https://insights.sbomify.com/GHSA-r97r-64vp-fghm/index.md)
```

## Sources

- OSV: https://osv.dev/vulnerability/GHSA-r97r-64vp-fghm

---
From sbomify Insights: https://insights.sbomify.com/GHSA-r97r-64vp-fghm/
Summaries are generated and may contain mistakes; the official description above is the record.