CVEvulnerability
CVE-2020-5224
8.8 HIGH
Official page ↗
- Status
- Modified
- Published
- 2020-01-24
- Last modified
- 2026-06-17
- Assigner
- [email protected]
- CVSS 3.1 ([email protected])
- 6.5 MEDIUM — CVSS:3.1/AV:N/AC:H/PR:L/UI:R/S:C/C:H/I:L/A:N
- CVSS 3.1 ([email protected])
- 8.8 HIGH — CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
- CVSS 2.0 ([email protected])
- 4.0 MEDIUM — AV:N/AC:L/Au:S/C:P/I:N/A:N
- Weaknesses
- CWE-287, CWE-326
Description
In Django User Sessions (django-user-sessions) before 1.7.1, the views provided allow users to terminate specific sessions. The session key is used to identify sessions, and thus included in the rendered HTML. In itself this is not a problem. However if the website has an XSS vulnerability, the session key could be extracted by the attacker and a session takeover could happen.
Affected configurations
• django-user-sessions project django-user-sessions (< 1.7.1)
Related
References
- https://github.com/Bouke/django-user-sessions/security/advisories/GHSA-5fq8-3q2f-4m5g Third Party Advisory
- https://github.com/jazzband/django-user-sessions/commit/f0c4077e7d1436ba6d721af85cee89222ca5d2d9 Patch
- https://github.com/Bouke/django-user-sessions/security/advisories/GHSA-5fq8-3q2f-4m5g Third Party Advisory
- https://github.com/jazzband/django-user-sessions/commit/f0c4077e7d1436ba6d721af85cee89222ca5d2d9 Patch