CVE-2026-23499 Saleor vulnerable to stored XSS via Unrestricted File Upload
Authenticated users can upload malicious files leading to stored XSS and token theft if media is served from the same domain without proper headers.
- 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
- None listed
What is CVE-2026-23499?
CVE-2026-23499 is a high-severity cross-site scripting vulnerability in saleor, published on 21 Jan 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
Saleor is an e-commerce platform. Starting in version 3.0.0 and prior to versions 3.20.108, 3.21.43, and 3.22.27, Saleor allowed authenticated staff users or Apps to upload arbitrary files, including malicious HTML and SVG files containing Javascript. Depending on the deployment strategy, these files may be served from the same domain as the dashboard without any restrictions leading to the execution of malicious scripts in the context of the user's browser. Malicious staff members could craft script injections to target other staff members, possibly stealing their access and/or refresh tokens. Users are vulnerable if they host the media files inside the same domain as the dashboard, e.g., dashboard is at `example.com/dashboard/` and media are under `example.com/media/`. They are not impact if media files are hosted in a different domain, e.g., `media.example.com`. Users are impacted if they do not return a `Content-Disposition: attachment` header for the media files. Saleor Cloud users are not impacted. This issue has been patched in versions: 3.22.27, 3.21.43, and 3.20.108. Some workarounds are available for those unable to upgrade. Configure the servers hosting the media files (e.g., CDN or reverse proxy) to return the Content-Disposition: attachment header. This instructs browsers to download the file instead of rendering them in the browser. Prevent the servers from returning HTML and SVG files. Set-up a `Content-Security-Policy` for media files, such as `Content-Security-Policy: default-src 'none'; base-uri 'none'; frame-ancestors 'none'; form-action 'none';`.
Which versions are affected by CVE-2026-23499?
It affects 1 product.
Products include Saleor Saleor.
How do I fix CVE-2026-23499?
No fix has been published for CVE-2026-23499 yet. Limit exposure of the affected software until one is available.
Escape output for the context it lands in and set a strict Content Security Policy. Upgrading the affected component is the real fix. More about Cross-site scripting.
Is CVE-2026-23499 being exploited?
There is no known exploitation of CVE-2026-23499 in the wild and no public exploit code.
Public exploit code: 1 proofs of concept on GitHub.
Other vulnerabilities in saleor
- CVE-2026-24136 Saleor has an Insecure Direct Object Reference (IDOR) in GraphQL API
- CVE-2026-33756 Saleor Affected by Denial of Service via Unbounded GraphQL Query Batching
- CVE-2026-35401 Saleor has a resource exhaustion vulnerability in GraphQL queries
- CVE-2026-22849 Saleor lacks proper HTML sanitization in rich text fields
- CVE-2023-26051 Saleor is vulnerable to staff-authenticated error message information disclosure vulnerability via Python exceptions
Sources
Also known as GHSA-666h-2p49-pg95.