CVE-2025-64459

Djangoproject Django SQL injection

9.1 CRITICALPublic exploitEPSS 19.3%

Published5 Nov 2025

Description

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.

CVSS 3.1 breakdown

Attack vectorNetwork

Attack complexityLow

Privileges requiredNone

User interactionNone

ScopeUnchanged

ConfidentialityHigh

IntegrityHigh

AvailabilityNone

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

Affected products

Djangoproject Django≥ 4.2 < 4.2.26 · ≥ 5.1 < 5.1.14 · ≥ 5.2 < 5.2.8

Remediation

Fixed in

Djangoproject Django≥ 4.2.26

Patch & vendor advisories

References

https://docs.djangoproject.com/en/dev/releases/security/Vendor Advisory
https://groups.google.com/g/django-announceMailing List
https://shivasurya.me/security/django/2025/11/07/django-sql-injection-CVE-2025-64459.htmlExploitThird Party Advisory
https://www.djangoproject.com/weblog/2025/nov/05/security-releases/Vendor Advisory

Related CVEs

Recent high-severity vulnerabilities sharing a weakness type.

Frequently asked

Is CVE-2025-64459 being actively exploited?

CVE-2025-64459 is not in the CISA KEV catalog. A public exploit reference exists, so treat it as exploitable. Its EPSS exploit probability is 19.3%.

How severe is CVE-2025-64459?

CVE-2025-64459 has a CVSS 3.1 base score of 9.1, rated critical. EPSS estimates a 19.3% probability of exploitation.

Which products are affected by CVE-2025-64459?

Affected products include Djangoproject Django.

How do I fix CVE-2025-64459?

Upgrade affected software to a fixed version, for example Djangoproject Django 4.2.26 or later, then confirm no affected versions remain in your inventory.

How Secuno handles this

Secuno correlates vulnerabilities like CVE-2025-64459 against the real software inventory on every managed device, as each hourly inventory arrives. Rather than a static severity, each match is scored in context: exploit availability, EPSS, the asset's exposure, and business criticality decide where it lands in the queue. If an affected version is present anywhere across your portfolio, it surfaces automatically with a prioritised remediation path.

See how prioritisation works Book a demo

Data from the NVD, CISA KEV catalog and FIRST EPSS. CVSS 3.1 base score shown where available.