{"answers":{"affected":"2 open source packages ship an affected version, including jellyfin-web. It affects 1 product.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2023-23635 exists.","fix":"Upgrade jellyfin-web to 10.8.4 or later.","what":"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."},"fix_prompt":"Check this codebase for CVE-2023-23635 and fix it if it is affected.\n\nWhat it is: 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.\nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2023-23635 exists.\n\nAffected packages and fixed versions:\n- jellyfin-web (npm): affected from 10.8.0; fixed in 10.8.4\n- jellyfin-web (npm): affected from 10.8.0; fixed in 10.8.4\n\nTask:\n1. 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.\n2. 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.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2023-23635/ (Markdown: https://insights.sbomify.com/CVE-2023-23635/index.md)","id":"CVE-2023-23635","markdown":"https://insights.sbomify.com/CVE-2023-23635/index.md","name":"CVE-2023-23635","record":{"aliases":["GHSA-749c-pc87-4qcw"],"analysis":{"component_type":"web_application","fix_type":"upgrade","impacts":["account_takeover","data_read"],"network_reachable":"yes","non_default_config":false,"product_category":"Jellyfin media server","requires_auth":"low_privilege","summary":"Stored XSS in Jellyfin collection names allows attackers to steal access tokens from victims' local storage.","user_interaction":"required","vuln_class":"xss"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"jellyfin","vendor":"jellyfin"}],"cvss":{"score":5.4,"severity":"medium","source":"cisa-adp","vector":"CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:N","version":"3.1"},"cwes":[{"id":"CWE-79","name":"Improper Neutralization of Input During Web Page Generation"}],"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.","ecosystems":["npm"],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"weaponised"},"has_fix":true,"headline":"Jellyfin Web Cross-Site Scripting (XSS) via Collection Name","id":"CVE-2023-23635","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"npm","product":null,"products":[],"type":"xss","year":"2023"},"n_packages":2,"n_references":3,"next":{"headline":"Jellyfin Web Cross-Site Scripting (XSS) via Playlist Name","id":"CVE-2023-23636"},"packages":[{"ecosystem":"npm","fixed":["10.8.4"],"introduced":["10.8.0"],"last_affected":[],"package":"jellyfin-web","purl":null,"source":"GHSA-749c-pc87-4qcw"},{"ecosystem":"npm","fixed":["10.8.4"],"introduced":["10.8.0"],"last_affected":[],"package":"jellyfin-web","purl":"pkg:npm/jellyfin-web","source":"GHSA-749c-pc87-4qcw"}],"prev":{"headline":"SQL injection in n/a","id":"CVE-2023-23634"},"products":["n/a"],"published":"2023-02-03","related":[{"cvss_score":10,"headline":"Jellyfin: Potential RCE via subtitle upload path traversal + .strm chain","id":"CVE-2026-35031","kev_date_added":null,"published":"2026-04-14"},{"cvss_score":10,"headline":"Jellyfin Possible Organization/Secret Compromise from dangerous CI implementation","id":"CVE-2026-31852","kev_date_added":null,"published":"2026-03-11"},{"cvss_score":9.3,"headline":"Jellyfin: Potential SSRF + Arbitrary file read via stream argument injection","id":"CVE-2026-35033","kev_date_added":null,"published":"2026-04-14"},{"cvss_score":9.1,"headline":"jellyfin-web has a stored cross-site scripting vulnerability in devices.js","id":"CVE-2023-30627","kev_date_added":null,"published":"2023-04-24"},{"cvss_score":8.8,"headline":"Jellyfin vulnerable to directory traversal and file write causing arbitrary code execution","id":"CVE-2023-30626","kev_date_added":null,"published":"2023-04-24"},{"cvss_score":8.8,"headline":"Incorrect Access Control and Cross Site Scripting in Jellyfin","id":"CVE-2022-35909","kev_date_added":null,"published":"2022-08-19"},{"cvss_score":8.6,"headline":"Jellyfin: Potential SSRF + Arbitrary file read via LiveTV M3U tuner","id":"CVE-2026-35032","kev_date_added":null,"published":"2026-04-14"}],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CC BY 4.0","name":"GitHub Advisory Database","prefix":"GHSA"},{"class":"attribution","licence":"US public information, NVD API terms","name":"NVD"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"no","exploitation":"poc","technical_impact":"total"},"state":"PUBLISHED","updated":"2025-03-26","vendors":["n/a"]},"summary":"Stored XSS in Jellyfin collection names allows attackers to steal access tokens from victims' local storage.","url":"https://insights.sbomify.com/CVE-2023-23635/"}