LiveActive security incident?Get immediate response
CVE Record

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

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.

MediumCVSS 5.4Not KEV-listedUpdated
Discuss exposureBack to CVEs
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

This is a stored cross-site scripting issue in Jellyfin collection names. A logged-in attacker could save malicious content as a collection name, causing script to run when another user views it. The cited CVE says this could steal access tokens from browser localStorage, so the main business risk is account compromise within an affected Jellyfin instance.

Executive priority

Treat this as a moderate-priority fix for affected Jellyfin systems. It is not listed as known exploited in the provided sources, but it can expose user access tokens and enable account misuse if an attacker has a low-privilege account.

Technical view

CVE-2023-23635 affects Jellyfin 10.8.x through 10.8.3. The vulnerable field is a collection name, creating stored XSS classified as CWE-79. CVSS 3.1 is 5.4 with network access, low complexity, low privileges, required user interaction, changed scope, and low confidentiality and integrity impact.

Likely exposure

Exposure is limited to Jellyfin deployments running 10.8.x through 10.8.3, especially where non-admin users can create or rename collections and other users view those collections in the web interface.

Exploitation context

The source bundle does not show CISA KEV listing or evidence of active exploitation. The CVE describes token theft from localStorage after a victim interacts with stored content. Exploitation requires an authenticated attacker and a victim viewing the affected collection name.

Researcher notes

The provided affected CPE data is incomplete, but the CVE title and description identify Jellyfin 10.8.x through 10.8.3. Avoid assuming broader product impact. Validate against upstream Jellyfin advisories or issue details before declaring exact fixed versions or exploit prevalence.

Mitigation direction

  • Identify any Jellyfin instances running 10.8.x through 10.8.3.
  • Check Jellyfin guidance and upgrade out of the affected version range.
  • Restrict collection creation or renaming to trusted users until remediated.
  • Invalidate or rotate exposed user sessions after suspected exploitation.
  • Review collection names for unexpected script-like content.

Validation and detection

  • Inventory Jellyfin versions across servers, containers, and hosted instances.
  • Confirm whether users can create or rename collections.
  • Review logs and audit trails for recent collection changes.
  • Test remediation by verifying collection names are safely rendered.
  • Check whether browser-stored tokens may need session invalidation.
Prepared
Confidence
medium
Sources
5

Public sources used

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-23635 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-23635Attack 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

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
n/an/an/aListed
Weakness

CWE details

CWE-79

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

CWE-79 · source CWE mapping

Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting')

Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.

Open CWE intelligenceSame-CWE CVEs