LiveActive security incident?Get immediate response
CVE Record

CVE-2023-23636: In Jellyfin 10.8.x through 10.8.3, the name of a playlist is vulnerable to stored XSS.

In Jellyfin 10.8.x through 10.8.3, the name of a playlist is vulnerable to stored XSS. This allows an attacker to steal access tokens from the localStorage of the victim.

MediumCVSS 5.4Not KEV-listedUpdated
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

Jellyfin versions 10.8.x through 10.8.3 allow a malicious playlist name to execute script in another user’s browser. The reported impact is theft of access tokens from localStorage, which could let an attacker act as the victim within Jellyfin.

Executive priority

Treat as a moderate-priority application security issue. It is not documented as actively exploited in the provided sources, but token theft can enable account impersonation where affected Jellyfin versions are used.

Technical view

This is a stored cross-site scripting issue in Jellyfin Web playlist names, classified as CWE-79. CVSS 3.1 is 5.4: network reachable, low attack complexity, low privileges required, user interaction required, changed scope, and low confidentiality and integrity impact.

Likely exposure

Exposure is limited to organizations running Jellyfin 10.8.x through 10.8.3, especially where untrusted or semi-trusted users can create or rename playlists viewed by others.

Exploitation context

The provided sources do not show CISA KEV listing or active exploitation. Exploitation requires a low-privileged attacker and victim interaction, such as viewing the stored playlist name in Jellyfin Web.

Researcher notes

Evidence identifies stored XSS in the playlist name field with token theft from localStorage as the stated impact. The provided bundle does not include exploit status, proof details, or explicit remediation text beyond affected version bounds and references.

Mitigation direction

  • Identify any Jellyfin instances running 10.8.x through 10.8.3.
  • Review Jellyfin advisory and issue guidance for the fixed release path.
  • Upgrade or remediate according to current Jellyfin vendor guidance.
  • Restrict playlist creation or renaming to trusted users until remediated.
  • Review suspicious playlist names and remove unsafe content.

Validation and detection

  • Inventory Jellyfin Web versions across internet-facing and internal deployments.
  • Confirm whether affected versions 10.8.x through 10.8.3 are present.
  • Check audit data for unexpected playlist creation or rename activity.
  • Verify remediated systems render playlist names as inert text.
  • Review browser-accessible token storage risk for impacted sessions.
Prepared
Confidence
high
Sources
4

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cwe · medium confidence lookup

CWE-79: User-session and phishing behavior lookup

Client-side and session-facing weaknesses should be reviewed alongside initial-access and user-execution behaviors. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2023-23636 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Medium
CVSS
5.4 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:N

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

1CVSS vectors
0Timeline events
0ADP providers
4Source links

CVSS vector scores

1 official score

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
5.4CVSS 3.1MediumCVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:N2.32.7Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

5.4Medium
CVSS 3.1 vector shape for CVE-2023-23636Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:N

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone
Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
n/an/an/aListed
Weakness

CWE details

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.