CVE-2022-35909 json
Incorrect Access Control and Cross Site Scripting in Jellyfin
published 4y ago modified 4mo ago also GHSA-qwp3-5fw3-5wgv , EUVD-2022-6613
- cvss
- 8.8
- version 3.1, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 1.7%
- EPSS 1.7% chance of exploitation in 30 days, percentile 77%
- public exploits
- 0
- none known
Summary
In Jellyfin before 10.8, the /users endpoint has incorrect access control for admin functionality.
Patch / fix
Is CVE-2022-35909 in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerExploit prediction
1.69% chance of exploitation in the next 30 days, higher than 77% of all scored CVEs (FIRST EPSS, 2026-11-09).
Exploits and checks
- docs.google.com https://docs.google.com/document/d/1cBXQrokCvWxKET4BKi3ZLtVp5gst6-MrGPgMKpfXw8Y/edit referenced PoC, tagged "exploit" by a source, unverified
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 3.1 | 8.8 | CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H |
| GitHub | 3.1 | 8.8 | CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H |
Affected packages
| ecosystem | package | affected | fixed in |
|---|---|---|---|
| nuget | Jellyfin.Common | <10.8.0 |
10.8.0 |
Classification
- Weakness
-
- CWE-79 Improper Neutralization of Input During Web Page Generation
References
-
github.com
/jellyfin/jellyfin/pull/7569/files
web, patch, third-party-advisory
-
docs.google.com
/document/d/1cBXQrokCvWxKET4BKi3ZLtVp5gst6-MrGPgMKpfXw8Y/edit
web, exploit, third-party-advisory
-
medium.com
/stolabs/cve-2022-35909-cve-2022-35910-incorrect-access-control-and-xss-stored-to-jellyfin-967359c91058
web, third-party-advisory
-
nvd.nist.gov
/vuln/detail/CVE-2022-35909
advisory
-
github.com
/jellyfin/jellyfin
package
Sources
- CVE List CVE-2022-35909
- GitHub Advisory GHSA-qwp3-5fw3-5wgv
- NVD CVE-2022-35909
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.