# GHSA-j982-5jv7-v43r: Silverstripe Form field validation message XSS vulnerability

> Attackers can inject malicious scripts via form validation messages in Silverstripe, potentially compromising user sessions.

- **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-j982-5jv7-v43r?

GHSA-j982-5jv7-v43r 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 high level XSS risk has been identified in the encoding of validation messages in certain FormField classes.

Certain fields such as the NumericField and DropdownField have been identified, but any form field which presents any invalid content as a part of its validation response will be at risk.

## Which versions are affected by GHSA-j982-5jv7-v43r?

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


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `silverstripe/framework` | Packagist | From 3.0.0 | 3.1.16 |
| `silverstripe/framework` | Packagist | From 3.0.0 | 3.1.16 |
| `silverstripe/framework` | Packagist | From 3.2.0 | 3.2.1 |
| `silverstripe/framework` | Packagist | From 3.2.0 | 3.2.1 |

## How do I fix GHSA-j982-5jv7-v43r?

Upgrade silverstripe/framework to a fixed version for your release line: 3.1.16 or 3.2.1.

## Is GHSA-j982-5jv7-v43r being exploited?

There is no known exploitation of GHSA-j982-5jv7-v43r in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for GHSA-j982-5jv7-v43r and fix it if it is affected.

What it is: GHSA-j982-5jv7-v43r 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-j982-5jv7-v43r in the wild and no public exploit code.

Affected packages and fixed versions:
- silverstripe/framework (Packagist): affected from 3.0.0; fixed in 3.1.16
- silverstripe/framework (Packagist): affected from 3.0.0; fixed in 3.1.16
- silverstripe/framework (Packagist): affected from 3.2.0; fixed in 3.2.1
- silverstripe/framework (Packagist): affected from 3.2.0; fixed in 3.2.1

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-j982-5jv7-v43r/ (Markdown: https://insights.sbomify.com/GHSA-j982-5jv7-v43r/index.md)
```

## Sources

- OSV: https://osv.dev/vulnerability/GHSA-j982-5jv7-v43r

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