CVE-2023-23635 Jellyfin Web Cross-Site Scripting (XSS) via Collection Name
Stored XSS in Jellyfin collection names allows attackers to steal access tokens from victims' local storage.
- 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
What is CVE-2023-23635?
CVE-2023-23635 is a medium-severity cross-site scripting vulnerability in n/a, published on 3 Feb 2023. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.
Official description
In Jellyfin 10.8.x through 10.8.3, the name of a collection is vulnerable to stored XSS. This allows an attacker to steal access tokens from the localStorage of the victim.
Weakness: CWE-79
Which versions are affected by CVE-2023-23635?
2 open source packages ship an affected version, including jellyfin-web. It affects 1 product.
| Package | Affected | Fixed in |
|---|---|---|
jellyfin-web npm | From 10.8.0 | 10.8.4 |
jellyfin-web npm | From 10.8.0 | 10.8.4 |
Products include Jellyfin Jellyfin.
How do I fix CVE-2023-23635?
Upgrade jellyfin-web to 10.8.4 or later.
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-2023-23635 being exploited?
It is not confirmed as exploited in the wild, but public exploit code for CVE-2023-23635 exists.
Other vulnerabilities in n/a
- CVE-2026-35031 Jellyfin: Potential RCE via subtitle upload path traversal + .strm chain
- CVE-2026-31852 Jellyfin Possible Organization/Secret Compromise from dangerous CI implementation
- CVE-2026-35033 Jellyfin: Potential SSRF + Arbitrary file read via stream argument injection
- CVE-2023-30627 jellyfin-web has a stored cross-site scripting vulnerability in devices.js
- CVE-2023-30626 Jellyfin vulnerable to directory traversal and file write causing arbitrary code execution
Sources
Also known as GHSA-749c-pc87-4qcw.