{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2023-30627 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2023-30627 yet. Limit exposure of the affected software until one is available.","what":"CVE-2023-30627 is a critical cross-site scripting vulnerability in jellyfin-web, published on 24 Apr 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-30627 and fix it if it is affected.\n\nWhat it is: CVE-2023-30627 is a critical cross-site scripting vulnerability in jellyfin-web, published on 24 Apr 2023. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.\nExploitation: There is no known exploitation of CVE-2023-30627 in the wild and no public exploit code.\n\nAffected product: jellyfin-web. No package-level version data is available, so check the vendor advisory linked from the reference page.\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-30627/ (Markdown: https://insights.sbomify.com/CVE-2023-30627/index.md)","id":"CVE-2023-30627","markdown":"https://insights.sbomify.com/CVE-2023-30627/index.md","name":"CVE-2023-30627","record":{"aliases":[],"analysis":{"component_type":"web_application","fix_type":"upgrade","impacts":["code_execution","privilege_escalation"],"network_reachable":"yes","non_default_config":false,"product_category":"Jellyfin web client","requires_auth":"low_privilege","summary":"Stored XSS in Jellyfin web client allows admin-privileged API calls, potentially leading to remote code execution when chained with other vulnerabilities.","user_interaction":"required","vuln_class":"xss"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[{"product":"jellyfin","vendor":"jellyfin"}],"cvss":{"score":9.1,"severity":"critical","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:H/I:H/A:H","version":"3.1"},"cwes":[{"id":"CWE-79","name":"Improper Neutralization of Input During Web Page Generation"}],"description":"jellyfin-web is the web client for Jellyfin, a free-software media system. Starting in version 10.1.0 and prior to version 10.8.10, a stored cross-site scripting vulnerability in device.js can be used to make arbitrary calls to the `REST` endpoints with admin privileges. When combined with CVE-2023-30626, this results in remote code execution on the Jellyfin instance in the context of the user who's running it. This issue is patched in version 10.8.10. There are no known workarounds.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":false,"headline":"jellyfin-web has a stored cross-site scripting vulnerability in devices.js","id":"CVE-2023-30627","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"xss","year":"2023"},"n_packages":0,"n_references":4,"next":{"headline":"Kiwi TCMS has command injection vulnerability in changelog.yml CI workflow","id":"CVE-2023-30628"},"packages":[],"prev":{"headline":"Jellyfin vulnerable to directory traversal and file write causing arbitrary code execution","id":"CVE-2023-30626"},"products":["jellyfin-web"],"published":"2023-04-24","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":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":"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":"none","technical_impact":"total"},"state":"PUBLISHED","updated":"2025-02-12","vendors":["jellyfin"]},"summary":"Stored XSS in Jellyfin web client allows admin-privileged API calls, potentially leading to remote code execution when chained with other vulnerabilities.","url":"https://insights.sbomify.com/CVE-2023-30627/"}