# GHSA-r32j-mr8p-hfp8: Silverstripe XSS in TreeDropdownField and TreeMultiSelectField

> An attacker with CMS access can inject malicious HTML into data sources, 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:** 23 May 2024

## What is GHSA-r32j-mr8p-hfp8?

GHSA-r32j-mr8p-hfp8 is a cross-site scripting vulnerability in silverstripe/framework, published on 23 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 TreeDropdownField and TreeMultiSelectField.

This vulnerability can only be exploited if a user with CMS access has posted malicious or unescaped HTML into any of the dataobjects used as a data source for either of these fields.

This has been resolved by ensuring that all dataobjects used as a data source have their content safely encoded.

## Which versions are affected by GHSA-r32j-mr8p-hfp8?

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


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

## How do I fix GHSA-r32j-mr8p-hfp8?

Upgrade silverstripe/framework to 3.1.10 or later.

## Is GHSA-r32j-mr8p-hfp8 being exploited?

There is no known exploitation of GHSA-r32j-mr8p-hfp8 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for GHSA-r32j-mr8p-hfp8 and fix it if it is affected.

What it is: GHSA-r32j-mr8p-hfp8 is a cross-site scripting vulnerability in silverstripe/framework, published on 23 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-r32j-mr8p-hfp8 in the wild and no public exploit code.

Affected packages and fixed versions:
- silverstripe/framework (Packagist): affected from 3.1.0; fixed in 3.1.10
- silverstripe/framework (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-r32j-mr8p-hfp8/ (Markdown: https://insights.sbomify.com/GHSA-r32j-mr8p-hfp8/index.md)
```

## Sources

- OSV: https://osv.dev/vulnerability/GHSA-r32j-mr8p-hfp8

---
From sbomify Insights: https://insights.sbomify.com/GHSA-r32j-mr8p-hfp8/
Summaries are generated and may contain mistakes; the official description above is the record.