Versions of the package djoser before 2.3.0 are vulnerable to Authentication Bypass when the authenticate() function fails. This is because the system falls back to querying the database directly, granting access to users with valid credentials, and eventually bypassing custom authentication checks such as two-factor authentication, LDAP validations, or requirements from configured AUTHENTICATION_BACKENDS.
CVE-2024-21543
HIGHNVD 7.17.1—
EchelonGraph scoreMEDIUM confidence
This high-severity CVE scores 7.1 under NVD CVSS v3. EPSS exploit probability: 0.6%, top 57% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).
Triggered by: NVD CVSS baseline
Sources: epss, nvd
7.1EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
- High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 1%CVSS: 7.1Exploit: None knownExposed: 0
A fix is available — apply it.
- CVSS v3
- 7.1
- EG Score
- 7.1(medium)
- EG Risk
- 32(Track)EG Risk 32/100SSVC: Track
EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).
How it’s computedSeverity71% × 45%Exploitation1% × 40%Automatability0% × 15%Action: Routine — remediate on your standard cadence. - EPSS PROB
- 1%
- EPSS %ILE
- 45%
- KEV
- Not listed
Published
December 13, 2024
Last Modified
April 15, 2026
References (6)
- report@snykhttps://github.com/sunscrapers/djoser/commit/d33c3993c0c735f23cbedc60fa59fce69354f19d
- report@snykhttps://github.com/sunscrapers/djoser/issues/795
- report@snykhttps://github.com/sunscrapers/djoser/pull/819
- report@snykhttps://github.com/sunscrapers/djoser/releases/tag/2.3.0
- report@snykhttps://security.snyk.io/vuln/SNYK-PYTHON-DJOSER-8366540
- af854a3a-2127-422b-91ae-364da2661108https://lists.debian.org/debian-lts-announce/2025/02/msg00023.html
Related CVEs
Related CVEs are temporarily unavailable — the same-product, same-vendor and same-CWE lists could not be loaded just now. That is not a sign that none exist; please retry shortly.
Frequently asked(5)
What is CVE-2024-21543?
CVE-2024-21543 is a high vulnerability published on December 13, 2024. Versions of the package djoser before 2.3.0 are vulnerable to Authentication Bypass when the authenticate() function fails. This is because the system falls back to querying the database directly, granting access to users with valid credentials, and eventually bypassing custom authentication checks…
When was CVE-2024-21543 disclosed?
CVE-2024-21543 was first published in the National Vulnerability Database on December 13, 2024, with the most recent update on April 15, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2024-21543 actively exploited?
CVE-2024-21543 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 1% probability of exploitation in the next 30 days, which ranks it in the top 55.3% of all scored CVEs.
What is the CVSS score of CVE-2024-21543?
CVE-2024-21543 has a CVSS v3 base score of 7.1 (NVD).
How do I remediate CVE-2024-21543?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2024-21543, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2024-21543
Is Your Infrastructure Affected by CVE-2024-21543?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.