# GHSA-779c-7w4p-2c4g: Silverstripe admin XSS Vulnerability via WYSIWYG editor

> Authenticated CMS users can inject malicious JavaScript via WYSIWYG editor attributes, potentially leading to session hijacking or code execution.

- **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-779c-7w4p-2c4g?

GHSA-779c-7w4p-2c4g is a cross-site scripting vulnerability in silverstripe/admin, 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

It is possible for a bad actor with access to the CMS to make use of onmouseover or onmouseout attributes in the WYSIWYG editor to embed malicious javascript.

## Which versions are affected by GHSA-779c-7w4p-2c4g?

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


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `silverstripe/admin` | Packagist | From 1.0.3 | 1.0.4 |
| `silverstripe/admin` | Packagist | From 1.0.3 | 1.0.4 |
| `silverstripe/admin` | Packagist | From 1.1.0 | 1.1.1 |
| `silverstripe/admin` | Packagist | From 1.1.0 | 1.1.1 |

## How do I fix GHSA-779c-7w4p-2c4g?

Upgrade silverstripe/admin to a fixed version for your release line: 1.0.4 or 1.1.1.

## Is GHSA-779c-7w4p-2c4g being exploited?

There is no known exploitation of GHSA-779c-7w4p-2c4g in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for GHSA-779c-7w4p-2c4g and fix it if it is affected.

What it is: GHSA-779c-7w4p-2c4g is a cross-site scripting vulnerability in silverstripe/admin, 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-779c-7w4p-2c4g in the wild and no public exploit code.

Affected packages and fixed versions:
- silverstripe/admin (Packagist): affected from 1.0.3; fixed in 1.0.4
- silverstripe/admin (Packagist): affected from 1.0.3; fixed in 1.0.4
- silverstripe/admin (Packagist): affected from 1.1.0; fixed in 1.1.1
- silverstripe/admin (Packagist): affected from 1.1.0; fixed in 1.1.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-779c-7w4p-2c4g/ (Markdown: https://insights.sbomify.com/GHSA-779c-7w4p-2c4g/index.md)
```

## Sources

- OSV: https://osv.dev/vulnerability/GHSA-779c-7w4p-2c4g

---
From sbomify Insights: https://insights.sbomify.com/GHSA-779c-7w4p-2c4g/
Summaries are generated and may contain mistakes; the official description above is the record.