# CVE-2026-117533: REDAXO 5.18.0 before 5.21.4 Stored XSS via Unsanitized Mediapool SVG Uploads


- **Severity:** Low 2.1 (`CVSS:4.0/AV:N/AC:H/AT:P/PR:L/UI:P/VC:L/VI:L/VA:N/SC:L/SI:L/SA:N`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 27 Oct 2026
- **Updated:** 27 Oct 2026
- **Also known as:** GHSA-2p3g-jr7p-qwwx, GHSA-7mw4-9872-fvq7

## What is CVE-2026-117533?

CVE-2026-117533 is a low-severity vulnerability in redaxo core, published on 27 Oct 2026. 

### Official description

REDAXO from 5.18.0 before 5.21.4 contains a stored cross-site scripting vulnerability because rex_media_service moves uploaded SVG files into the public media folder before sanitizing them. Authenticated users with mediapool upload rights can race the sanitizer or exhaust memory limits to leave script-laden SVGs publicly served, executing scripts in victims' backend sessions.

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

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


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

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

## Is CVE-2026-117533 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-117533 is a low-severity vulnerability in redaxo core, published on 27 Oct 2026. 
Exploitation: There is no known exploitation of CVE-2026-117533 in the wild and no public exploit code.

Affected product: redaxo core. 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-117533/ (Markdown: https://insights.sbomify.com/CVE-2026-117533/index.md)
```

## Sources

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

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