SQL injection protection via ORM in Django - Performance & Optimization

Performance: SQL injection protection via ORM

HIGH IMPACT

This concept affects page load speed indirectly by preventing costly database errors and security breaches that can degrade user experience.

Safely querying a database to avoid SQL injection

Django

from django.db import connection

user_input = "'; DROP TABLE users; --"
query = "SELECT * FROM users WHERE username = %s"
with connection.cursor() as cursor:
    cursor.execute(query, [user_input])
    results = cursor.fetchall()

Using parameterized queries safely escapes user input, preventing injection and avoiding costly database errors.

📈 Performance GainPrevents server errors that block responses, maintaining fast and reliable page loads.

Safely querying a database to avoid SQL injection

Django

from django.db import connection

user_input = "'; DROP TABLE users; --"
query = f"SELECT * FROM users WHERE username = '{user_input}'"
with connection.cursor() as cursor:
    cursor.execute(query)
    results = cursor.fetchall()

Directly embedding user input into raw SQL strings allows attackers to inject malicious SQL, risking data loss and server errors.

📉 Performance CostCan cause database errors that block response, increasing server response time and degrading user experience.

Performance Comparison

Pattern	DOM Operations	Reflows	Paint Cost	Verdict
Raw SQL with string interpolation	N/A	N/A	N/A	[X] Bad
Parameterized queries with ORM	N/A	N/A	N/A	[OK] Good

Rendering Pipeline

SQL injection protection via ORM affects the backend database query stage before rendering. Proper parameterization prevents errors that could delay or block the server response, indirectly improving frontend rendering speed.

→Backend Query Execution

→Server Response Preparation

⚠️ BottleneckDatabase query errors causing server delays

Optimization Tips

1Never embed user input directly into raw SQL strings.

2Use ORM methods or parameterized queries to safely escape inputs.

3Preventing SQL injection avoids costly server errors that delay page loads.

Performance Quiz - 3 Questions

Why does using raw SQL with string interpolation harm performance?

A It triggers extra CSS reflows

B It increases DOM nodes on the page

C It can cause database errors that block server responses

D It adds large JavaScript bundles

DevTools: Network

How to check: Open DevTools, go to Network tab, reload the page, and check server response times and error codes.

What to look for: Look for HTTP 500 errors or slow responses indicating backend query failures.

Practice

1. Which of the following best explains how Django ORM protects against SQL injection?

easy

A. It automatically escapes user inputs when building queries.

B. It disables all user inputs by default.

C. It requires manual escaping of inputs in queries.

D. It converts all queries to raw SQL strings.

Solution

1. Step 1: Understand Django ORM query building

   Django ORM builds SQL queries by safely escaping user inputs automatically.

2. Step 2: Compare options with ORM behavior

   Only automatic escaping matches Django ORM's protection against SQL injection.

3. Final Answer:

   It automatically escapes user inputs when building queries. -> Option A

4. Quick Check:

   Django ORM auto-escapes inputs = C [OK]

Hint: Remember: ORM escapes inputs automatically to prevent injection [OK]

Common Mistakes:

• Thinking ORM disables inputs
• Believing manual escaping is needed
• Assuming ORM uses raw SQL strings

2. Which Django ORM method is safe to use for filtering records with user input?

easy

A. Model.objects.raw(f"SELECT * FROM table WHERE name = '{user_input}'")

B. Model.objects.filter("name = " + user_input)

C. Model.objects.filter(name=user_input)

D. Model.objects.execute_sql("SELECT * FROM table WHERE name = " + user_input)

Solution

1. Step 1: Identify safe ORM filtering syntax

   Model.objects.filter(name=user_input) uses ORM's parameter binding and escapes input safely.

2. Step 2: Analyze other options for unsafe practices

   Options A, B, and C build raw SQL strings or invalid syntax, risking injection.

3. Final Answer:

   Model.objects.filter(name=user_input) -> Option C

4. Quick Check:

   Use filter() with keyword args for safe queries = D [OK]

Hint: Use filter() with keyword arguments, not raw SQL strings [OK]

Common Mistakes:

• Using raw SQL with string concatenation
• Passing raw SQL strings to filter()
• Ignoring ORM's parameter binding

3. What will be the output of this Django ORM query if user_input = "Robert'); DROP TABLE users;--"?

users = User.objects.filter(username=user_input)
print(users.query)

medium

A. A raw SQL query that deletes the users table

B. An empty query with no filtering

C. A syntax error due to unescaped quotes

D. A safe SQL query with escaped input preventing injection

Solution

1. Step 1: Understand ORM query with dangerous input

   ORM escapes dangerous characters in user_input to prevent SQL injection.

2. Step 2: Analyze printed query behavior

   Printed query shows safe SQL with escaped input, not raw injection or errors.

3. Final Answer:

   A safe SQL query with escaped input preventing injection -> Option D

4. Quick Check:

   ORM escapes dangerous input = B [OK]

Hint: ORM escapes dangerous input, so injection won't happen [OK]

Common Mistakes:

• Assuming raw SQL runs as is
• Expecting syntax errors from quotes
• Thinking ORM ignores dangerous input

4. Identify the error in this Django ORM code that tries to prevent SQL injection:

query = "SELECT * FROM users WHERE username = '%s'" % user_input
users = User.objects.raw(query)

medium

A. The raw() method automatically escapes inputs, so no error.

B. Using raw SQL with string formatting allows SQL injection.

C. The filter() method should be used instead of raw().

D. The query string is missing parameter placeholders.

Solution

1. Step 1: Analyze string formatting with user input

   Using % formatting inserts user_input directly, risking SQL injection.

2. Step 2: Understand raw() method behavior

   raw() executes raw SQL without escaping, so injection risk remains.

3. Final Answer:

   Using raw SQL with string formatting allows SQL injection. -> Option B

4. Quick Check:

   String formatting + raw() = injection risk = A [OK]

Hint: Never build raw SQL with string formatting; use ORM methods [OK]

Common Mistakes:

• Assuming raw() escapes inputs
• Using raw SQL instead of filter()
• Ignoring injection risk in string formatting

5. You want to safely filter users by email domain using Django ORM. Which approach correctly prevents SQL injection?

user_domain = request.GET.get('domain')
# Which code is safe?
A) User.objects.filter(email__endswith=user_domain)
B) User.objects.raw(f"SELECT * FROM users WHERE email LIKE '%{user_domain}'")
C) User.objects.filter(email__endswith='%' + user_domain)
D) User.objects.raw("SELECT * FROM users WHERE email LIKE '%" + user_domain + "'")

hard

A. User.objects.filter(email__endswith=user_domain)

B. User.objects.raw(f"SELECT * FROM users WHERE email LIKE '%{user_domain}'")

C. User.objects.filter(email__endswith='%' + user_domain)

D. User.objects.raw("SELECT * FROM users WHERE email LIKE '%" + user_domain + "'")

Solution

1. Step 1: Identify safe ORM filtering for email domain

   Using filter() with email__endswith=user_domain safely escapes input and builds query.

2. Step 2: Analyze raw() and string concatenation risks

   Options B and D use raw SQL with string interpolation, risking injection. User.objects.filter(email__endswith='%' + user_domain) incorrectly adds '%' in Python string, not ORM pattern.

3. Final Answer:

   User.objects.filter(email__endswith=user_domain) -> Option A

4. Quick Check:

   Use ORM filter with lookup for safe input handling = A [OK]

Hint: Use ORM lookups like __endswith, avoid raw SQL with user input [OK]

Common Mistakes:

• Using raw SQL with user input directly
• Adding SQL wildcards in Python strings
• Ignoring ORM's safe query building