How severe is CVE-2024-22513?

No CVSS score has been assigned to CVE-2024-22513 yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by CVE-2024-22513?

CVE-2024-22513 affects the following packages: djangorestframework-simplejwt (PyPI). Ecosystems affected: PyPI.

How do I fix CVE-2024-22513?

Update djangorestframework-simplejwt to 5.5.1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2024-22513 is resolved across your whole dependency graph.

How do I detect CVE-2024-22513 in my PyPI dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for djangorestframework-simplejwt, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate CVE-2024-22513 if there is no patch (or I can't update yet)?

If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

How does O3 Security protect against CVE-2024-22513?

O3 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like CVE-2024-22513 can be triaged on real exposure rather than presence alone.

Is CVE-2024-22513 actively exploited in the wild?

Yes. There are 1 known exploit references for CVE-2024-22513, including 1 documented proof-of-concept exploit on Exploit-DB. Treat this as actively exploitable and prioritize patching immediately. All exploit code should only be run in an isolated sandbox environment for research or authorized testing — never against production systems without explicit written authorization.

What is the EPSS score for CVE-2024-22513?

CVE-2024-22513 has an EPSS (Exploit Prediction Scoring System) score of 0.8%, placing it in the 55th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

What type of vulnerability is CVE-2024-22513?

CVE-2024-22513 is classified as Missing Authentication (CWE-306). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was CVE-2024-22513 published, and has it been updated?

CVE-2024-22513 was published on March 16, 2024 and was last updated on July 7, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

🐍 PyPI

Not in CISA KEV

CVE-2024-22513 — djangorestframework-simpl…

Fix: jazzband/djangorestframework-simplejwt#872

CVE-2024-22513 is a Missing Authentication vulnerability in djangorestframework-simplejwt. 1 public exploit reference exists, so weaponization risk is real. A fix is available for djangorestframework-simplejwt — see the affected versions and patch details below.

Improper Privilege Management in djangorestframework-simplejwt

Also known asGHSA-5vcc-86wm-547qPYSEC-2026-1305

Published

Mar 16, 2024

Updated

Jul 7, 2026

Affected

1 pkg

Patched

1 / 1

Exploits

1 known

Exploitation data as of Sep 23, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

Exploitation Status

No confirmed exploitation observed yet

CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.

Exploitation and automatability from CISA’s SSVC triage for CVE-2024-22513.

EPSS Exploitation Probability

via FIRST.org ↗

0.8%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs55th percentile — riskier than 55% of all scored CVEsHighest risk

EPSS (Exploit Prediction Scoring System) is a daily probability model maintained by FIRST.org. It estimates the likelihood a CVE will be exploited in production environments within the next 30 days, derived from real-world threat intelligence signals.

Real-World Exposure

1 pkg affected

🐍djangorestframework-simplejwt

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects PyPI packages — download data is not available via public APIs for these ecosystems.

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.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
🐍PyPI	`djangorestframework-simplejwt`	all versions	5.5.1`pip install --upgrade 'djangorestframework-simplejwt==5.5.1'`

Exploits & PoCs

Research use only. For defensive security, authorized penetration testing, and academic research only. Never execute exploit code against systems without explicit written authorization.

EDB-51992webappspython

djangorestframework-simplejwt 5.3.1 - Information Disclosure

by Dhrumil Mistry · Apr 15, 2024

Exploit-DB Source

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for djangorestframework-simplejwt, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update djangorestframework-simplejwt to 5.5.1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2024-22513 is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
How O3 protects you
O3 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like CVE-2024-22513 can be triaged on real exposure rather than presence alone.

Tailored to CVE-2024-22513. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

O3 Security · Impact-Aware SCA

Is CVE-2024-22513 in your dependencies?

O3 Security finds CVE-2024-22513 across PyPI dependencies, including transitive ones, and its impact-aware SCA ranks findings by whether your code actually calls the vulnerable path.

Scan my dependencies How O3 SCA works