# GHSA-97jm-g33h-f46g: silverstripe/framework ReadOnly transformation for formfields exploitable

> Reflected XSS in SilverStripe readonly form fields allows attackers to execute scripts via crafted URLs when form validation errors occur.

- **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-97jm-g33h-f46g?

GHSA-97jm-g33h-f46g 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

Form fields returning isReadonly() as true are vulnerable to reflected XSS injections. This includes ReadonlyField, LookupField, HTMLReadonlyField, as well as special purpose fields like TimeField_Readonly. Values submitted to through these form fields are not filtered out from the form session data, and might be shown to the user depending on the form behaviour. For example, form validation errors cause the form to re-render with previously submitted values by default.

SilverStripe forms automatically load values from request data (GET and POST), which enables malicious use of URLs if your form uses these fields and doesn't overwrite data on form construction.

Readonly and disabled form fields are already filtered out in Form->saveInto(), so maliciously submitted data on these fields doesn't make it into the database unless you are accessing form values directly in your saving logic.

## Which versions are affected by GHSA-97jm-g33h-f46g?

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


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `silverstripe/framework` | Packagist | All versions | 3.1.21 |
| `silverstripe/framework` | Packagist | All versions | 3.1.21 |
| `silverstripe/framework` | Packagist | From 3.2.0 | 3.2.6 |
| `silverstripe/framework` | Packagist | From 3.2.0 | 3.2.6 |
| `silverstripe/framework` | Packagist | From 3.3.0 | 3.3.4 |
| `silverstripe/framework` | Packagist | From 3.3.0 | 3.3.4 |
| `silverstripe/framework` | Packagist | From 3.4.0 | 3.4.2 |
| `silverstripe/framework` | Packagist | From 3.4.0 | 3.4.2 |

## How do I fix GHSA-97jm-g33h-f46g?

Upgrade silverstripe/framework to a fixed version for your release line: 3.1.21, 3.2.6, 3.3.4 or 3.4.2.

## Is GHSA-97jm-g33h-f46g being exploited?

There is no known exploitation of GHSA-97jm-g33h-f46g in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for GHSA-97jm-g33h-f46g and fix it if it is affected.

What it is: GHSA-97jm-g33h-f46g 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-97jm-g33h-f46g in the wild and no public exploit code.

Affected packages and fixed versions:
- silverstripe/framework (Packagist): affected all versions; fixed in 3.1.21
- silverstripe/framework (Packagist): affected all versions; fixed in 3.1.21
- silverstripe/framework (Packagist): affected from 3.2.0; fixed in 3.2.6
- silverstripe/framework (Packagist): affected from 3.2.0; fixed in 3.2.6
- silverstripe/framework (Packagist): affected from 3.3.0; fixed in 3.3.4
- silverstripe/framework (Packagist): affected from 3.3.0; fixed in 3.3.4
- silverstripe/framework (Packagist): affected from 3.4.0; fixed in 3.4.2
- silverstripe/framework (Packagist): affected from 3.4.0; fixed in 3.4.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-97jm-g33h-f46g/ (Markdown: https://insights.sbomify.com/GHSA-97jm-g33h-f46g/index.md)
```

## Sources

- OSV: https://osv.dev/vulnerability/GHSA-97jm-g33h-f46g

---
From sbomify Insights: https://insights.sbomify.com/GHSA-97jm-g33h-f46g/
Summaries are generated and may contain mistakes; the official description above is the record.