VulnerabilityPublished 10 Jul 2024Updated 4 Nov 2025

CVE-2024-39329: django · Timing Side Channel

Affects djangoSource CVE Database V5

Not known to be exploited · CVSS 5.3 Medium : upgrade to 5.0.7 or 4.2.14 when convenient.

Data as of 26 Oct 2026, 11:07 UTC

CVSS 3.1 base score

5.3Medium

How severe the flaw is on the 0–10 CVSS scale.

EPSS: 0.8% chance of exploitation in 30 days – higher than 59% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch: Available – fixed in 5.0.7, 4.2.14

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N

Attack Vector: Network
Attack Complexity: Low
Privileges Required: None
User Interaction: None
Scope: Unchanged
Confidentiality: Low
Integrity: None
Availability: None

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Network: The vulnerable component is bound to the network stack and the set of possible attackers extends beyond the other options listed, up to and including the entire Internet. Such a vulnerability is often termed 'remotely exploitable' and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers).
Attack Complexity: Low: Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success against the vulnerable component.
Privileges Required: None: The attacker is unauthorized prior to attack, and therefore does not require any access to settings or files to carry out an attack.
User Interaction: None: The vulnerable system can be exploited without any interaction from any user.
Scope: Unchanged: An exploited vulnerability can only affect resources managed by the same security authority. In this case, the vulnerable component and the impacted component are either the same, or both are managed by the same security authority.
Confidentiality: Low: There is some loss of confidentiality. Access to some restricted information is obtained, but the attacker does not have control over what information is obtained, or the amount or kind of loss is limited. The information disclosure does not cause a direct, serious loss to the impacted component.
Integrity: None: There is no loss of integrity within the impacted component.
Availability: None: There is no impact to availability within the impacted component.

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 10 Jul 2024
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

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.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC or the CVSS exploit maturity reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Upgrade django to 5.0.7 or 4.2.14.

Affected software

Product	Affected	Fixed in
PyPIdjango`pkg:pypi/django`Other threats	Affected <5.0.7 <4.2.14	Fixed in 5.0.7 4.2.14

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

AI-suggested

The primary mitigation is to upgrade Django installations to version 5.0.7 or 4.2.14 or later, where the timing discrepancy has been fixed. Organizations should audit their web applications to identify any usage of affected Django versions and plan timely patching. In addition to upgrading, developers can implement application-level mitigations such as adding consistent response delays or using constant-time comparison functions to reduce timing side channels. Monitoring authentication logs for unusual login attempts or patterns indicative of user enumeration can help detect exploitation attempts. Employing web application firewalls (WAFs) with rules to detect and block rapid, repeated login attempts may also reduce risk. Finally, organizations should review password policies and consider disabling or carefully managing accounts with unusable passwords to minimize attack surface.

Description

An issue was discovered in Django 5.0 before 5.0.7 and 4.2 before 4.2.14. The django.contrib.auth.backends.ModelBackend.authenticate() method allows remote attackers to enumerate users via a timing attack involving login requests for users with an unusable password.

Impact

For European organizations, this vulnerability primarily threatens the confidentiality of user account information by enabling attackers to enumerate valid usernames remotely. User enumeration can facilitate subsequent attacks such as credential stuffing, phishing, or brute force attempts, increasing the overall risk to organizational security. Web applications built on affected Django versions that handle sensitive user data or provide access to critical services are particularly at risk. While the vulnerability does not directly compromise data integrity or availability, the exposure of valid usernames can aid attackers in crafting more effective attacks, potentially leading to account compromise or unauthorized access. Organizations in sectors with high regulatory requirements for data protection, such as finance, healthcare, and government, may face compliance risks if user data is indirectly exposed. The lack of known exploits in the wild reduces immediate risk, but the ease of exploitation and the widespread use of Django in Europe necessitate prompt remediation to prevent exploitation.

CWE-208Observable Timing Discrepancy (opens in a new tab)
Base weakness
Two separate operations in a product require different amounts of time to complete, in a way that is observable to an actor and reveals security-relevant information about the state of the product, such as whether a particular operation was successful or not.
OWASP Cheat Sheets
Error Handling (opens in a new tab)
Logging (opens in a new tab)
OWASP ASVS 4.0.3
V8.3.4 (opens in a new tab)
V14.3.3 (opens in a new tab)
V7.3.3 (opens in a new tab)
Attack patterns
Cross-Domain Search Timing (opens in a new tab)
Application Fingerprinting (opens in a new tab)
System Footprinting (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 4 Nov 2025, 17:13 UTC

WeaknessesCWE-208

Technical details

References

Community reviews

Related threats