CVE-2020-5224

What it is

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.

At a glance

Exploitability

Can be exploited over the network with a low-privilege account, but needs a user to act. High risk of data exposure.

Exploit odds

0.5% chance of exploitation in the next 30 days (EPSS).

Fix

A patch, advisory or fixed version is referenced. Upgrade or apply it.

Timeline

1. 2020-01-24 20:15 UTC PublishedDisclosed publicly on CVE.org and NVD
2. 2026-06-17 03:21 UTC Last updatedMost recent change to the record

Why it ranks here

• Exploited in the wild: no, CISA does not list it.
• Exploit odds: 0.5% in the next 30 days (EPSS).
• Severity: 6.5 MEDIUM (CVSS).
• Fix: a patch or advisory is linked.

Details

Published

2020-01-24 20:15 UTC

Last modified

2026-06-17 03:21 UTC

Exploit probability

0.5% · EPSS, next 30 days

Weakness

CWE-287 · Improper authentication

Record status

Modified

Affected

• django-user-sessions Project django-user-sessions < 1.7.1

Attack profile CVSS 3.1 · 6.5

Attack vector

Network

Complexity

High

Privileges needed

Low

User interaction

Required

Scope

Changed

Confidentiality

High

Integrity

Low

Availability

None

Is it in your code?

Hand this to your coding agent. It searches your project for the affected products and checks versions. Nothing leaves your machine.

Read https://cve-list.com/agent/cve/CVE-2020-5224.md and follow it. Check whether this project is affected by CVE-2020-5224. Read only. Don't change anything and don't upload my code. Tell me yes, no or not sure, with the file as proof.

Copy as ticket · More options · Status badge