CVE-2025-59681
BaseFortify
Publication date: 2025-10-01
Last updated on: 2025-11-04
Assigner: MITRE
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| djangoproject | django | From 4.2 (inc) to 4.2.25 (exc) |
| djangoproject | django | From 5.1 (inc) to 5.1.13 (exc) |
| djangoproject | django | From 5.2 (inc) to 5.2.7 (exc) |
Helpful Resources
Exploitability
| CWE ID | Description |
|---|---|
| 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. Without sufficient removal or quoting of SQL syntax in user-controllable inputs, the generated SQL query can cause those inputs to be interpreted as SQL instead of ordinary user data. |
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?
This vulnerability is a SQL injection issue in Django versions before 4.2.25, 5.1 before 5.1.13, and 5.2 before 5.2.7. It occurs in the QuerySet methods annotate(), alias(), aggregate(), and extra() when column aliases are constructed using a specially crafted dictionary with dictionary expansion as keyword arguments. This affects applications using MySQL and MariaDB databases.
How can this vulnerability impact me? :
The vulnerability can allow an attacker to perform SQL injection attacks, potentially leading to unauthorized access to or modification of database data. This can compromise the confidentiality and integrity of the data, especially on MySQL and MariaDB databases used by the affected Django versions.