How severe is CVE-2025-59681?

CVE-2025-59681 has a CVSS 3.x base score of 7.1, rated high severity. It is exploitable over network with high attack complexity, requires low privileges and no user interaction. Impact on confidentiality is high, integrity low, and availability none.

Is CVE-2025-59681 being actively exploited?

It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 1% (45th percentile), an estimate of the probability of exploitation in the next 30 days.

What products are affected by CVE-2025-59681?

CVE-2025-59681 affects Djangoproject Django. See the affected-products list for the exact vulnerable versions.

How do I fix CVE-2025-59681?

Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround. Given its high severity, prioritise patching exposed systems.

Does CVE-2025-59681 have an EU (EUVD) identifier?

Yes. CVE-2025-59681 is tracked in the ENISA EU Vulnerability Database (EUVD) as EUVD-2025-32691.

When was CVE-2025-59681 published?

CVE-2025-59681 was published on 2025-10-01 and last updated on 2026-06-17.

CVE-2025-59681

CVE-2025-59681 is a high-severity vulnerability in Djangoproject Django with a CVSS 3.x base score of 7.1. It is not currently listed as actively exploited by CISA, and its EPSS exploit-prediction score is low. The underlying weakness is classified as CWE-89.

Key facts

Severity: High (CVSS 3.x base score 7.1)
EPSS exploit prediction: 1% (45th percentile)
Actively exploited: Not listed in CISA KEV
EU (EUVD) id: EUVD-2025-32691
Weakness: CWE-89
Affected product: Djangoproject Django
Published: 2025-10-01
Last modified: 2026-06-17

Description

An issue was discovered in Django 4.2 before 4.2.25, 5.1 before 5.1.13, and 5.2 before 5.2.7. QuerySet.annotate(), QuerySet.alias(), QuerySet.aggregate(), and QuerySet.extra() are subject to SQL injection in column aliases, when using a suitably crafted dictionary, with dictionary expansion, as the **kwargs passed to these methods (on MySQL and MariaDB).

Frequently asked questions

What is CVE-2025-59681?: An issue was discovered in Django 4.2 before 4.2.25, 5.1 before 5.1.13, and 5.2 before 5.2.7. QuerySet.annotate(), QuerySet.alias(), QuerySet.aggregate(), and QuerySet.extra() are subject to SQL injection in column aliases, when using a suitably crafted dictionary, with dictionary expansion, as the **kwargs passed to these methods (on MySQL and MariaDB).
How severe is CVE-2025-59681?: CVE-2025-59681 has a CVSS 3.x base score of 7.1, rated high severity. It is exploitable over network with high attack complexity, requires low privileges and no user interaction. Impact on confidentiality is high, integrity low, and availability none.
Is CVE-2025-59681 being actively exploited?: It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 1% (45th percentile), an estimate of the probability of exploitation in the next 30 days.
What products are affected by CVE-2025-59681?: CVE-2025-59681 affects Djangoproject Django. See the affected-products list for the exact vulnerable versions.
How do I fix CVE-2025-59681?: Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround. Given its high severity, prioritise patching exposed systems.
Does CVE-2025-59681 have an EU (EUVD) identifier?: Yes. CVE-2025-59681 is tracked in the ENISA EU Vulnerability Database (EUVD) as EUVD-2025-32691.
When was CVE-2025-59681 published?: CVE-2025-59681 was published on 2025-10-01 and last updated on 2026-06-17.

References

Affected products (1)

cpe:2.3:a:djangoproject:django:*:*:*:*:*:*:*:*

More vulnerabilities in Djangoproject Django

CVE-2014-0474 — Critical (CVSS 10.0): The (1) FilePathField, (2) GenericIPAddressField, and (3) IPAddressField model field classes in Django before 1.4.11,…
CVE-2026-4277 — Critical (CVSS 9.8): An issue was discovered in 6.0 before 6.0.4, 5.2 before 5.2.13, and 4.2 before 4.2.30. Add permissions on inline model…
CVE-2024-53908 — Critical (CVSS 9.8): An issue was discovered in Django 5.1 before 5.1.4, 5.0 before 5.0.10, and 4.2 before 4.2.17. Direct usage of the…
CVE-2023-31047 — Critical (CVSS 9.8): In Django 3.2 before 3.2.19, 4.x before 4.1.9, and 4.2 before 4.2.1, it was possible to bypass validation when using…
CVE-2022-34265 — Critical (CVSS 9.8): An issue was discovered in Django 3.2 before 3.2.14 and 4.0 before 4.0.6. The Trunc() and Extract() database functions…
CVE-2022-28347 — Critical (CVSS 9.8): A SQL injection issue was discovered in QuerySet.explain() in Django 2.2 before 2.2.28, 3.2 before 3.2.13, and 4.0…

All CVEs affecting Djangoproject Django →

Other CWE-89 (SQL Injection) vulnerabilities

CVE-2026-20030 — Critical (CVSS 10.0): As part of Cisco's ongoing commitment to proactive security and product quality, the Cisco Crosswork engineering team…
CVE-2026-72811 — Critical (CVSS 10.0): SiYuan versions <= v3.7.2 contain a SQL injection vulnerability in the backlink/mention search query…
CVE-2026-72851 — Critical (CVSS 10.0): Budibase before 3.40.0 contains an unauthenticated SQL injection vulnerability in webhook-triggered automations with…
CVE-2026-72899 — Critical (CVSS 10.0): Metabase allows an unauthenticated attacker to inject arbitrary SQL via a publicly shared card or dashboard that…
CVE-2026-72898 — Critical (CVSS 10.0): Metabase allows a remote, unauthenticated attacker to inject arbitrary SQL via the '/reset_password' database endpoint…
CVE-2026-48330 — Critical (CVSS 10.0): Adobe Campaign Classic (ACC) is affected by an Improper Neutralization of Special Elements used in an SQL Command ('SQL…

Browse all CWE-89 (SQL Injection) vulnerabilities →