Django up to 4.2.25/5.1.13/5.2.7 QuerySet.filter/QuerySet.exclude/QuerySet.get sql injection

Summaryinfo

A vulnerability was found in Django up to 4.2.25/5.1.13/5.2.7. It has been rated as critical. Affected is the function QuerySet.filter/QuerySet.exclude/QuerySet.get. Performing a manipulation results in sql injection. This vulnerability is known as CVE-2025-64459. Remote exploitation of the attack is possible. Furthermore, an exploit is available. Upgrading the affected component is advised.

Detailsinfo

A vulnerability, which was classified as critical, was found in Django up to 4.2.25/5.1.13/5.2.7. This affects the function QuerySet.filter/QuerySet.exclude/QuerySet.get. The manipulation with an unknown input leads to a sql injection vulnerability. CWE is classifying the issue as CWE-89. The product constructs all or part of an SQL command using externally-influenced input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could modify the intended SQL command when it is sent to a downstream component. This is going to have an impact on confidentiality, integrity, and availability. The summary by CVE is:

An issue was discovered in 5.1 before 5.1.14, 4.2 before 4.2.26, and 5.2 before 5.2.8. The methods `QuerySet.filter()`, `QuerySet.exclude()`, and `QuerySet.get()`, and the class `Q()`, are subject to SQL injection when using a suitably crafted dictionary, with dictionary expansion, as the `_connector` argument. 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 cyberstan for reporting this issue.

It is possible to read the advisory at docs.djangoproject.com. This vulnerability is uniquely identified as CVE-2025-64459 since 11/04/2025. The exploitability is told to be easy. It is possible to initiate the attack remotely. Technical details and a public exploit are known. The attack technique deployed by this issue is T1505 according to MITRE ATT&CK.

The exploit is shared for download at exploit-db.com. It is declared as proof-of-concept. The vulnerability scanner Nessus provides a plugin with the ID 274081 (Linux Distros Unpatched Vulnerability : CVE-2025-64459), which helps to determine the existence of the flaw in a target environment.

Upgrading to version 4.2.26, 5.1.14 or 5.2.8 eliminates this vulnerability. The upgrade is hosted for download at docs.djangoproject.com.

The vulnerability is also documented in the databases at Exploit-DB (52456), Tenable (274081), EUVD (EUVD-2025-37763) and CERT Bund (WID-SEC-2025-2495). Statistical analysis made it clear that VulDB provides the best quality 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
• 5.1.0
• 5.1.1
• 5.1.2
• 5.1.3
• 5.1.4
• 5.1.5
• 5.1.6
• 5.1.7
• 5.1.8
• 5.1.9
• 5.1.10
• 5.1.11
• 5.1.12
• 5.1.13
• 5.2.0
• 5.2.1
• 5.2.2
• 5.2.3
• 5.2.4
• 5.2.5
• 5.2.6
• 5.2.7

License

• open-source

CPE 2.3info

• 🔒
• 🔒
• 🔒

CPE 2.2info

• 🔒
• 🔒
• 🔒

CVSSv4info

CVSSv3info

CVSSv2info

Exploitinginfo

Threat Intelligenceinfo

Countermeasuresinfo

Timelineinfo

Sourcesinfo

Entryinfo

Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.

Discussion