CVE-2020-5224
low-risk
Published 2020-01-24
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.
Do I need to act?
-
0.13% chance of exploitation
EPSS score — low exploit probability
-
Not on CISA KEV list
No confirmed active exploitation reported to CISA
?
Patch status unknown
Check vendor advisories for fix availability and mitigation guidance
6
CVSS 6.5/10
Medium
NETWORK
/ HIGH complexity
Affected Products (1)
Django-User-Sessions
Affected Vendors
References (4)
Third Party Advisory
https://github.com/Bouke/django-user-sessions/security/advisories/GHSA-5fq8-3q2f...
Third Party Advisory
https://github.com/Bouke/django-user-sessions/security/advisories/GHSA-5fq8-3q2f...
26
/ 100
low-risk
Severity
20/34 · Moderate
Exploitability
1/34 · Minimal
Exposure
5/34 · Minimal