# CVE-2024-43801: Privilege escalation to admin from a low-privileged user via SVG upload in Jellyfin > Low-privileged users can escalate to admin via stored XSS in SVG profile images if admins view them externally, exposing access tokens. - **Severity:** Medium 4.6 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:U/C:L/I:L/A:N`) - **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:** No - **Published:** 2 Sep 2024 - **Updated:** 3 Sep 2024 - **Also known as:** GHSA-vcmh-9wx9-rfqh ## What is CVE-2024-43801? CVE-2024-43801 is a medium-severity cross-site scripting vulnerability in jellyfin, published on 2 Sep 2024. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link. ### Official description Jellyfin is an open source self hosted media server. The Jellyfin user profile image upload accepts SVG files, allowing for a stored XSS attack against an admin user via a specially crafted malicious SVG file. When viewed by an admin outside of the Jellyfin Web UI (e.g. via "view image" in a browser), this malicious SVG file could interact with the browser's LocalStorage and retrieve an AccessToken, which in turn can be used in an API call to elevate the target user to a Jellyfin administrator. The actual attack vector is unlikely to be exploited, as it requires specific actions by the administrator to view the SVG image outside of Jellyfin's WebUI, i.e. it is not a passive attack. The underlying exploit mechanism is solved by PR #12490, which forces attached images (including the potential malicious SVG) to be treated as attachments and thus downloaded by browsers, rather than viewed. This prevents exploitation of the LocalStorage of the browser. This PR has been merged and the relevant code changes are included in release version 10.9.10. All users are advised to upgrade. Weakness: CWE-200 (Exposure of Sensitive Information to an Unauthorized Actor) ## Which versions are affected by CVE-2024-43801? It affects 1 product. Products: Jellyfin Jellyfin. ## How do I fix CVE-2024-43801? No fix has been published for CVE-2024-43801 yet. Limit exposure of the affected software until one is available. ## Is CVE-2024-43801 being exploited? There is no known exploitation of CVE-2024-43801 in the wild and no public exploit code. ## Other vulnerabilities in jellyfin - [CVE-2026-35031](https://insights.sbomify.com/CVE-2026-35031/): Jellyfin: Potential RCE via subtitle upload path traversal + .strm chain (critical 10.0) - [CVE-2026-31852](https://insights.sbomify.com/CVE-2026-31852/): Jellyfin Possible Organization/Secret Compromise from dangerous CI implementation (critical 10.0) - [CVE-2026-35033](https://insights.sbomify.com/CVE-2026-35033/): Jellyfin: Potential SSRF + Arbitrary file read via stream argument injection (critical 9.3) - [CVE-2023-30627](https://insights.sbomify.com/CVE-2023-30627/): jellyfin-web has a stored cross-site scripting vulnerability in devices.js (critical 9.1) - [CVE-2023-30626](https://insights.sbomify.com/CVE-2023-30626/): Jellyfin vulnerable to directory traversal and file write causing arbitrary code execution (high 8.8) ## Fix prompt for AI coding agents ```text Check this codebase for CVE-2024-43801 and fix it if it is affected. What it is: CVE-2024-43801 is a medium-severity cross-site scripting vulnerability in jellyfin, published on 2 Sep 2024. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link. Exploitation: There is no known exploitation of CVE-2024-43801 in the wild and no public exploit code. Affected product: jellyfin. No package-level version data is available, so check the vendor advisory linked from the reference page. Task: 1. 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. 2. 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. 3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead. 4. Run the tests and summarise what changed and why. 5. If nothing in the project is affected, say so and change nothing. Reference: https://insights.sbomify.com/CVE-2024-43801/ (Markdown: https://insights.sbomify.com/CVE-2024-43801/index.md) ``` ## Sources - CVE record: https://www.cve.org/CVERecord?id=CVE-2024-43801 - NVD: https://nvd.nist.gov/vuln/detail/CVE-2024-43801 - OSV: https://osv.dev/vulnerability/CVE-2024-43801 --- From sbomify Insights: https://insights.sbomify.com/CVE-2024-43801/ Summaries are generated and may contain mistakes; the official description above is the record.