Skip to main content
VulnerabilityPublished Updated

CVE-2024-22513: djangorestframework-simplejwt · Missing Authentication

Affects djangorestframework-simplejwtSource CVE Database V5

0

Public exploit available (Exploit-DB) · CVSS 5.5 Medium.

Data as of 26 Oct 2026, 12:54 UTC

CVSS 3.1 base score
5.5Medium
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.8% chance of exploitation in 30 days – higher than 56% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N

Exploitation evidence

t = 0 is the CVE’s publication on cve.org

  1. Disclosed: evidence found.

    CVE published 16 Mar 2024

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  4. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

Timeline

  1. CVE ID reserved

    by MITRE Corporation

    , 65 days before disclosure

  2. CVE published

    on cve.org

    , t = 0

  3. First Exploit-DB entry (opens in a new tab)

    djangorestframework-simplejwt 5.3.1 - Information Disclosure

    , 30 days after disclosure

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

What to do

Affected software

ProductAffectedFixed in
PyPIdjangorestframework-simplejwtpkg:pypi/djangorestframework-simplejwtOther threatsAffected
  • <=5.3.1
Fixed in–

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

To mitigate CVE-2024-22513, organizations should upgrade djangorestframework-simplejwt to a version that includes proper user validation checks in the for_user method once available. In the absence of an official patch, developers should implement custom validation logic to verify the active status of user accounts during JWT token processing, ensuring disabled users are denied access. Additionally, auditing and monitoring authentication logs for anomalous access patterns from disabled accounts can help detect exploitation attempts. Applying the principle of least privilege to user accounts and promptly disabling or removing inactive accounts reduces exposure. Organizations should also review their JWT authentication workflows to confirm that user status checks are enforced consistently. Finally, maintaining an up-to-date inventory of dependencies and subscribing to security advisories for critical libraries like djangorestframework-simplejwt is essential for timely response to vulnerabilities.

Description

djangorestframework-simplejwt version 5.3.1 and before is vulnerable to information disclosure. A user can access web application resources even after their account has been disabled due to missing user validation checks via the for_user method.

References

Community reviews

Loading reviews…