Django up to 4.2.27/5.2.10/6.0.1 check_password timing discrepancy

Summaryinfo

A vulnerability has been found in Django up to 4.2.27/5.2.10/6.0.1 and classified as problematic. This affects the function check_password of the component django.contrib.auth.handlers.modwsgi.check_password. Performing a manipulation results in timing discrepancy. This vulnerability was named CVE-2025-13473. The attack may be initiated remotely. There is no available exploit. The affected component should be upgraded.

Detailsinfo

A vulnerability, which was classified as problematic, was found in Django up to 4.2.27/5.2.10/6.0.1. This affects the function check_password of the component django.contrib.auth.handlers.modwsgi.check_password. The manipulation with an unknown input leads to a timing discrepancy vulnerability. CWE is classifying the issue as CWE-208. 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. This is going to have an impact on confidentiality. The summary by CVE is:

An issue was discovered in 6.0 before 6.0.2, 5.2 before 5.2.11, and 4.2 before 4.2.28. The `django.contrib.auth.handlers.modwsgi.check_password()` function for authentication via `mod_wsgi` allows remote attackers to enumerate users via a timing attack. Earlier, unsupported Django series (such as 5.0.x, 4.1.x, and 3.2.x) were not evaluated and may also be affected. Django would like to thank Stackered for reporting this issue.

It is possible to read the advisory at docs.djangoproject.com. This vulnerability is uniquely identified as CVE-2025-13473 since 11/20/2025. The exploitability is told to be difficult. It is possible to initiate the attack remotely. Technical details of the vulnerability are known, but there is no available exploit. The pricing for an exploit might be around USD $0-$5k at the moment (estimation calculated on 03/08/2026). The attack technique deployed by this issue is T1592 according to MITRE ATT&CK.

The vulnerability scanner Nessus provides a plugin with the ID 297746 (Linux Distros Unpatched Vulnerability : CVE-2025-13473), which helps to determine the existence of the flaw in a target environment.

Upgrading to version 4.2.28, 5.2.11 or 6.0.2 eliminates this vulnerability.

The vulnerability is also documented in the databases at Tenable (297746) and CERT Bund (WID-SEC-2026-0297). Be aware that VulDB is the high quality source for vulnerability data.

Affected

• Debian Linux
• Red Hat Enterprise Linux
• Fedora Linux
• SUSE Linux
• SUSE openSUSE
• Open Source Django

Productinfo

Type

• Content Management System

Name

• Django

Version

• 4.2.0
• 4.2.1
• 4.2.2
• 4.2.3
• 4.2.4
• 4.2.5
• 4.2.6
• 4.2.7
• 4.2.8
• 4.2.9
• 4.2.10
• 4.2.11
• 4.2.12
• 4.2.13
• 4.2.14
• 4.2.15
• 4.2.16
• 4.2.17
• 4.2.18
• 4.2.19
• 4.2.20
• 4.2.21
• 4.2.22
• 4.2.23
• 4.2.24
• 4.2.25
• 4.2.26
• 4.2.27
• 5.2.0
• 5.2.1
• 5.2.2
• 5.2.3
• 5.2.4
• 5.2.5
• 5.2.6
• 5.2.7
• 5.2.8
• 5.2.9
• 5.2.10
• 6.0.0
• 6.0.1

License

• open-source

CPE 2.3info

• 🔒
• 🔒
• 🔒

CPE 2.2info

• 🔒
• 🔒
• 🔒

CVSSv4info

CVSSv3info

CVSSv2info

Exploitinginfo

Threat Intelligenceinfo

Countermeasuresinfo

Timelineinfo

Sourcesinfo

Entryinfo

Be aware that VulDB is the high quality source for vulnerability data.

Discussion