# CVE-2026-90561: Strapi 4.x through 4.26.2 and 5.x before 5.48.1 Stored XSS via WYSIWYG

> Stored XSS in Strapi WYSIWYG allows Authors to execute scripts in Editor or Admin sessions, leading to account takeover.

- **Severity:** Critical 9.3 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:P/VC:H/VI:H/VA:N/SC:H/SI:H/SA:N`)
- **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:** No
- **Published:** 13 Sep 2026
- **Updated:** 24 Sep 2026
- **Also known as:** GHSA-jh7v-p6jw-jwhc

## What is CVE-2026-90561?

CVE-2026-90561 is a critical cross-site scripting vulnerability in strapi, published on 13 Sep 2026. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.

### Official description

Strapi versions 4.x through 4.26.2 and 5.x before 5.48.1 contain a stored cross-site scripting vulnerability in the content manager WYSIWYG preview component that fails to strip script tags from rich text. An Author-role user can store malicious script tags in rich text fields that execute in an Editor or Super Admin's session when the preview pane is expanded, enabling account takeover.

Weakness: CWE-79 (Improper Neutralization of Input During Web Page Generation)

## Which versions are affected by CVE-2026-90561?


## How do I fix CVE-2026-90561?

No fix has been published for CVE-2026-90561 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-90561 being exploited?

There is no known exploitation of CVE-2026-90561 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-90561 and fix it if it is affected.

What it is: CVE-2026-90561 is a critical cross-site scripting vulnerability in strapi, published on 13 Sep 2026. 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 CVE-2026-90561 in the wild and no public exploit code.

Affected product: strapi. No package-level version data is available, so check the vendor advisory linked from the reference page.

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/CVE-2026-90561/ (Markdown: https://insights.sbomify.com/CVE-2026-90561/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-90561
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-90561
- OSV: https://osv.dev/vulnerability/CVE-2026-90561

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-90561/
Summaries are generated and may contain mistakes; the official description above is the record.