CVE-2020-5224: In Django User Sessions (django-user-sessions) before 1.7.1, the views provided allow users to terminate speci

Q: How do I fix CVE-2020-5224?

django-user-sessions: upgrade to 1.7.1. Exact commands for each OS are on this page.

Q: Is CVE-2020-5224 being exploited?

CVE-2020-5224 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

Q: What does CVE-2020-5224 affect?

CVE-2020-5224 affects django-user-sessions. Severity is medium (CVSS 6.5). 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 proble

Q: How urgent is CVE-2020-5224?

Priority 34/100. No elevated risk signals yet.

Routine

MEDIUM 6.5UPGRADE

CVE-2020-5224 is a medium-severity flaw (CVSS 6.5) affecting django-user-sessions. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

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.

Why this priority

No elevated risk signals yet

A fixed release or distro patch exists.

Risk facts

CVSS score	6.5 (Medium)
Attack vector	Network (remote)
Attack complexity	High
Privileges needed	Low
User interaction	Required
EPSS exploit chance	0.5% (top 55%)
CISA exploited list	No
Weakness	CWE-287, CWE-326
Published	2020-01-24
Last modified	2026-06-17

Publisher (CNA): GitHub, Inc. · Vendor: django-user-sessions project

Last updated 2026-06-17 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score

Am I affected?

Timeline

2020-01-24 20:15 UTCPublished CVE record published
2026-06-17 03:21 UTCUpdated Record last modified

django-user-sessions project django-user-sessions UPGRADE

Affected: < 1.7.1

Fixed in: 1.7.1

Safe to downgrade to: no unaffected older release

1. Check installed version

apt-cache policy django-user-sessions || rpm -q django-user-sessions || django-user-sessions --version

2. UPGRADE to 1.7.1 (Debian / Ubuntu)

sudo apt update && sudo apt install --only-upgrade django-user-sessions

2. UPGRADE (RHEL / Amazon Linux / Fedora)

sudo dnf upgrade django-user-sessions

Note

Distros often backport fixes without changing the version number. Confirm with the distro advisory or changelog.

Verify at the official source NVD · CVE Program · Report a problem with this page
Scores and fixes here are computed automatically from those and other public sources. Confirm with the vendor advisory before changing production systems.

Quick answers

How do I fix CVE-2020-5224?

django-user-sessions: upgrade to 1.7.1. Exact commands for each OS are on this page.

Is CVE-2020-5224 being exploited?

CVE-2020-5224 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

What does CVE-2020-5224 affect?

CVE-2020-5224 affects django-user-sessions. Severity is medium (CVSS 6.5). 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 proble

How urgent is CVE-2020-5224?

Priority 34/100. No elevated risk signals yet.

Software pages

Django vulnerabilities

References

← Back to latest CVEs