| Property | |
|---|---|
| Language |  |
| Severity |  |
| CWE | CWE-89: Improper Neutralization of Special Elements used in an SQL Command (‘SQL Injection’) |
| OWASP | A01:2017 - Injection |
| Confidence Level | Low |
| Impact Level | High |
| Likelihood Level | Low |
Using raw or non-parameterized SQL queries (such as RawSQL or .raw()) in Django can expose your application to SQL injection attacks. This happens when user input is included directly in SQL statements without proper handling, allowing attackers to manipulate queries.
| Property | |
|---|---|
| Language | |
| Severity | |
| CWE | CWE-89: Improper Neutralization of Special Elements used in an SQL Command (‘SQL Injection’) |
| OWASP | A01:2017 - Injection |
| Confidence Level | Low |
| Impact Level | High |
| Likelihood Level | Low |
Using custom expressions with the ‘as_sql’ method can be dangerous if any user input is included without proper sanitization. This can allow attackers to inject malicious SQL code into your database queries.
If exploited, attackers could read, modify, or delete sensitive data in the database, bypass authentication, or gain unauthorized access. This could lead to data breaches, loss of data integrity, and compromise of the entire application.
| Property | |
|---|---|
| Language | |
| Severity |  |
| CWE | CWE-89: Improper Neutralization of Special Elements used in an SQL Command (‘SQL Injection’) |
| OWASP | A01:2017 - Injection |
| Confidence Level | Medium |
| Impact Level | High |
| Likelihood Level | Medium |
User input from HTTP requests is being passed directly into Django’s raw() SQL queries without proper sanitization or parameterization. This allows attackers to inject malicious SQL code, making your application vulnerable to SQL injection.
If exploited, attackers can access, modify, or delete data in your database, potentially exposing sensitive information, corrupting data, or gaining unauthorized access to user accounts. This can lead to data breaches, loss of user trust, and significant harm to your organization.
| Property | |
|---|---|
| Language | |
| Severity | |
| CWE | CWE-89: Improper Neutralization of Special Elements used in an SQL Command (‘SQL Injection’) |
| OWASP | A01:2017 - Injection |
| Confidence Level | Medium |
| Impact Level | High |
| Likelihood Level | Medium |
User input from web requests is being directly included in the SQL ‘where’ clause via Django’s ’extra()’ method without proper sanitization or parameterization. This allows attackers to inject malicious SQL code, making the query vulnerable to SQL injection.
| Property | |
|---|---|
| Language | |
| Severity | |
| CWE | CWE-89: Improper Neutralization of Special Elements used in an SQL Command (‘SQL Injection’) |
| OWASP | A01:2017 - Injection |
| Confidence Level | Medium |
| Impact Level | High |
| Likelihood Level | Medium |
User input from HTTP requests is being directly included in SQL queries executed via cursor.execute(), instead of using Django’s parameterized QuerySets. This makes the code vulnerable to SQL injection because attackers can manipulate the query through crafted input.
| Property | |
|---|---|
| Language | |
| Severity | |
| CWE | CWE-89: Improper Neutralization of Special Elements used in an SQL Command (‘SQL Injection’) |
| OWASP | A01:2017 - Injection |
| Confidence Level | Medium |
| Impact Level | High |
| Likelihood Level | Medium |
User input from HTTP requests is being used directly in RawSQL queries without proper sanitization or parameterization. This allows attackers to inject malicious SQL code by manipulating request data.
If exploited, an attacker could execute arbitrary SQL commands against your database—leading to data leaks, unauthorized data modification or deletion, and potentially full compromise of the application’s data layer. This puts sensitive information and system integrity at severe risk.
| Property | |
|---|---|
| Language | |
| Severity | |
| CWE | CWE-89: Improper Neutralization of Special Elements used in an SQL Command (‘SQL Injection’) |
| OWASP | A01:2017 - Injection |
| Confidence Level | Medium |
| Impact Level | High |
| Likelihood Level | Medium |
User input is being directly inserted into SQLAlchemy query clauses like group_by, order_by, distinct, having, or filter without proper parameter binding. This allows attackers to inject malicious SQL code if untrusted data reaches these clauses.
If exploited, attackers could manipulate database queries to access, modify, or delete sensitive data, bypass authentication, or disrupt application functionality. This could lead to data breaches, data loss, or full compromise of the application’s database.
| Property | |
|---|---|
| Language | |
| Severity | |
| CWE | CWE-89: Improper Neutralization of Special Elements used in an SQL Command (‘SQL Injection’) |
| OWASP | A01:2017 - Injection |
| Confidence Level | Medium |
| Impact Level | High |
| Likelihood Level | Low |
User input is being directly inserted into SQL clauses like group_by, order_by, distinct, having, or filter in SQLAlchemy without proper parameter binding. This allows attackers to manipulate SQL queries by injecting malicious input.
Exploiting this vulnerability could let an attacker run arbitrary SQL commands against your database, potentially exposing, altering, or deleting sensitive data. It can result in data breaches, data loss, or unauthorized access to application functionality.
| Property | |
|---|---|
| Language | |
| Severity | |
| CWE | CWE-89: Improper Neutralization of Special Elements used in an SQL Command (‘SQL Injection’) |
| OWASP | A01:2017 - Injection |
| Confidence Level | Low |
| Impact Level | High |
| Likelihood Level | Low |
Building SQL queries by directly concatenating or formatting untrusted input into SQL strings can allow attackers to inject malicious SQL code. This insecure practice makes your code vulnerable to SQL injection attacks.
If exploited, an attacker could manipulate database queries to access, modify, or delete data, bypass authentication, or execute administrative operations. This can lead to data breaches, data loss, or full compromise of the application’s database.
| Property | |
|---|---|
| Language | |
| Severity |  |
| CWE | CWE-89: Improper Neutralization of Special Elements used in an SQL Command (‘SQL Injection’) |
| OWASP | A01:2017 - Injection |
| Confidence Level | Medium |
| Impact Level | Low |
| Likelihood Level | Low |
Building SQL queries by concatenating or formatting user input into strings and passing them to sqlalchemy.text() can allow attackers to inject malicious SQL code. This approach bypasses SQLAlchemy’s built-in protections, making your code vulnerable to SQL injection.