CVE-2025-64459
Last modified
CVE-2025-64459 is a critical-severity vulnerability rated 9.1/10 on the CVSS scale. 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.. EPSS estimates a 19.14% chance of exploitation in the next 30 days.
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.
Metrics
Weakness Enumeration
Affected Software
| Vendor | Product | Versions |
|---|---|---|
| Djangoproject | Django | >= 4.2, < 4.2.26 |
| Djangoproject | Django | >= 5.1, < 5.1.14 |
| Djangoproject | Django | >= 5.2, < 5.2.8 |
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.htmlExploit, Third Party Advisory
Timeline
- Published
- Last Modified
- Status
- Analyzed
Frequently Asked Questions
What is CVE-2025-64459?
How severe is CVE-2025-64459?
How do I fix CVE-2025-64459?
How Strix Helps
- How Strix found a critical auth bypass in etcdStrix autonomously discovered a critical authentication bypass in etcd, later designated CVE-2026-33413.
- Autonomous PentestingAI agents that find and validate exploitable vulnerabilities like this one across your applications.
- PR ReviewsPentest every pull request so vulnerable code is caught before it ships to production.
- AI Penetration TestingHow AI-driven penetration testing continuously covers your attack surface.
Related CVEs from 2025
- CVE-2025-64453Rejected reason: Not used
- CVE-2025-64454Rejected reason: Not used
- CVE-2025-64455Rejected reason: Not used
- CVE-2025-64456In JetBrains ReSharper before 2025.2.4 missing signature ver…7.8
- CVE-2025-64457In JetBrains ReSharper, Rider and dotTrace before 2025.2.5 l…7
- CVE-2025-64458An issue was discovered in 5.1 before 5.1.14, 4.2 before 4.2…7.5
- CVE-2025-6446A vulnerability, which was classified as critical, has been …9.8
- CVE-2025-64460An issue was discovered in 5.2 before 5.2.9, 5.1 before 5.1.…7.5
- CVE-2025-64461There is an out of bounds write vulnerability in NI LabVIEW …8.5
- CVE-2025-64462There is an out of bounds read vulnerability in NI LabVIEW i…8.5
- CVE-2025-64463There is an out of bounds read vulnerability in NI LabVIEW i…8.5
- CVE-2025-64464There is an out of bounds read vulnerability in NI LabVIEW i…8.5
Are you affected by CVE-2025-64459?
Run a free Strix scan to check your systems for this vulnerability.
Scan your code nowSource: NVD / NIST