CSRF protection mechanism in Django - Interactive Code Practice

Practice - 5 Tasks

1fill in blank

easy

Complete the code to include CSRF protection in a Django template form.

Django

<form method="post">\n  [1]\n  <input type="submit" value="Submit">\n</form>

Drag options to blanks, or click blank then click option'

A{% csrf_field %}

B{% csrf_protect %}

C{% csrf_token %}

D{% csrf_input %}

Attempts:

3 left

💡 Hint

Common Mistakes

Using incorrect template tags like {% csrf_protect %} inside the form.

Forgetting to include the CSRF token tag inside POST forms.

In Django templates, {% csrf_token %} adds the CSRF token inside forms to protect against CSRF attacks.

2fill in blank

medium

Complete the Django view decorator to enable CSRF protection.

Django

from django.views.decorators.csrf import [1]\n\n@[1]\ndef my_view(request):\n    # view code here\n    pass

Drag options to blanks, or click blank then click option'

Acsrf_protect

Bcsrf_token

Ccsrf_exempt

Dcsrf_check

Attempts:

3 left

💡 Hint

Common Mistakes

Using 'csrf_exempt' which disables CSRF protection.

Confusing the decorator with the template tag.

The csrf_protect decorator enforces CSRF protection on a Django view.

3fill in blank

hard

Fix the error in the middleware setting to enable CSRF protection.

Django

MIDDLEWARE = [\n    'django.middleware.security.SecurityMiddleware',\n    'django.contrib.sessions.middleware.SessionMiddleware',\n    [1],\n    'django.middleware.common.CommonMiddleware',\n]

Drag options to blanks, or click blank then click option'

A'django.middleware.csrf.CsrfMiddleware'

B'django.middleware.csrf.CsrfViewMiddleware'

C'django.middleware.security.CsrfViewMiddleware'

D'django.middleware.csrf.CsrfProtectionMiddleware'

Attempts:

3 left

💡 Hint

Common Mistakes

Using incorrect middleware class names that do not exist.

Placing the middleware in the wrong order.

The correct middleware class for CSRF protection is django.middleware.csrf.CsrfViewMiddleware.

4fill in blank

hard

Fill both blanks to create a dictionary comprehension that filters POST data keys starting with 'csrf'.

Django

csrf_data = {key: value for key, value in request.POST.items() if key.[1]('csrf') and value [2] ''}

Drag options to blanks, or click blank then click option'

Astartswith

Bendswith

C!=

D==

Attempts:

3 left

💡 Hint

Common Mistakes

Using 'endswith' instead of 'startswith' for keys.

Using '==' instead of '!=' to filter values.

The method startswith checks if keys start with 'csrf'. The operator != ensures values are not empty strings.

5fill in blank

hard

Fill all three blanks to create a safe form submission check in a Django view.

Django

if request.method == '[1]' and request.POST.get('[2]') == '[3]':\n    # process form data

Drag options to blanks, or click blank then click option'

APOST

Bcsrfmiddlewaretoken

Cvalid_token

DGET

Attempts:

3 left

💡 Hint

Common Mistakes

Checking for 'GET' method instead of 'POST'.

Using wrong CSRF token field name.

Comparing token to wrong value.

Check if the request method is 'POST', then verify the CSRF token field named 'csrfmiddlewaretoken' matches a valid token.

Practice

1. What is the main purpose of Django's CSRF protection mechanism?

easy

A. To prevent unauthorized websites from making unwanted requests on behalf of a user

B. To speed up the loading time of web pages

C. To encrypt user passwords in the database

D. To improve the visual design of forms

Solution

1. Step 1: Understand CSRF meaning

   CSRF stands for Cross-Site Request Forgery, which is an attack where unauthorized sites trick users into submitting unwanted requests.

2. Step 2: Identify Django's CSRF role

   Django's CSRF protection stops these attacks by verifying a secret token in forms, ensuring requests come from trusted sources.

3. Final Answer:

   To prevent unauthorized websites from making unwanted requests on behalf of a user -> Option A

4. Quick Check:

   CSRF protection = prevent unwanted cross-site requests [OK]

Hint: CSRF stops other sites from faking your form submissions [OK]

Common Mistakes:

• Confusing CSRF with password encryption
• Thinking CSRF speeds up page loading
• Believing CSRF improves form design

2. Which of the following is the correct way to include CSRF protection in a Django HTML form?

easy

A.

B. {% csrf_token %}

C. {% csrf %}

D. <csrf_token>

Solution

1. Step 1: Recall Django template syntax for CSRF

   Django uses the template tag {% csrf_token %} inside forms to insert the CSRF token as a hidden input automatically.

2. Step 2: Check each option's correctness

   <form method='post'>{% csrf_token %}</form> uses the correct Django template tag. Options B and C use incorrect tags. <form method='post'><input type='hidden' name='csrfmiddlewaretoken'></form> misses the token value and tag.

3. Final Answer:

   <form method='post'>{% csrf_token %}</form> -> Option B

4. Quick Check:

   Use {% csrf_token %} inside POST forms [OK]

Hint: Use {% csrf_token %} exactly inside POST forms [OK]

Common Mistakes:

• Using incorrect template tags like {% csrf %}
• Forgetting to add the token inside the form
• Trying to add CSRF token manually without the tag

3. Given this Django view and template snippet, what happens if the CSRF token is missing in the POST request?

def submit_view(request):
    if request.method == 'POST':
        return HttpResponse('Success')
    return render(request, 'form.html')



  
  Send

medium

A. The form will automatically add the CSRF token

B. The POST request will succeed and return 'Success'

C. The server will crash with an exception

D. The POST request will be rejected with a 403 Forbidden error

Solution

1. Step 1: Understand CSRF token role in POST

   Django requires a valid CSRF token in POST requests to prevent forgery attacks.

2. Step 2: Analyze missing token effect

   Since the form omits {% csrf_token %}, the POST request lacks the token, so Django rejects it with a 403 Forbidden error.

3. Final Answer:

   The POST request will be rejected with a 403 Forbidden error -> Option D

4. Quick Check:

   Missing CSRF token = 403 error [OK]

Hint: Missing CSRF token in POST causes 403 error [OK]

Common Mistakes:

• Assuming POST succeeds without token
• Thinking server crashes instead of 403
• Believing token is added automatically

4. You have a Django form that raises a CSRF verification failed error. Which of the following is the most likely cause?

medium

A. The {% csrf_token %} tag is missing inside the form

B. The form uses GET method instead of POST

C. The form action URL is incorrect

D. The form has no submit button

Solution

1. Step 1: Identify cause of CSRF verification failure

   CSRF verification fails when the token is missing or invalid in POST requests.

2. Step 2: Check each option's relevance

   Missing the {% csrf_token %} tag inside the form causes the token to be absent from the request. Options A, C, and D do not directly cause CSRF errors.

3. Final Answer:

   The {% csrf_token %} tag is missing inside the form -> Option A

4. Quick Check:

   Missing {% csrf_token %} causes CSRF failure [OK]

Hint: Always include {% csrf_token %} in POST forms [OK]

Common Mistakes:

• Thinking GET method causes CSRF errors
• Blaming wrong form action for CSRF failure
• Assuming submit button absence triggers CSRF error

5. You want to protect an AJAX POST request in Django from CSRF attacks. Which approach correctly includes the CSRF token in the request headers?

hard

A. Disable CSRF middleware for AJAX requests

B. Include {% csrf_token %} inside the AJAX data payload as a form field

C. Add the CSRF token value from the cookie to the 'X-CSRFToken' header in the AJAX request

D. Send the CSRF token as a URL query parameter

Solution

1. Step 1: Understand CSRF protection for AJAX

   Django expects the CSRF token in the 'X-CSRFToken' header for AJAX POST requests, usually read from the CSRF cookie.

2. Step 2: Evaluate options for AJAX token inclusion

   Add the CSRF token value from the cookie to the 'X-CSRFToken' header in the AJAX request correctly adds the token from the cookie to the header. Include {% csrf_token %} inside the AJAX data payload as a form field is incorrect because {% csrf_token %} is a template tag, not usable in JS. Disable CSRF middleware for AJAX requests disables protection (unsafe). Send the CSRF token as a URL query parameter is insecure and not recommended.

3. Final Answer:

   Add the CSRF token value from the cookie to the 'X-CSRFToken' header in the AJAX request -> Option C

4. Quick Check:

   AJAX CSRF token goes in 'X-CSRFToken' header [OK]

Hint: Send CSRF token in 'X-CSRFToken' header for AJAX POST [OK]

Common Mistakes:

• Trying to use {% csrf_token %} in JavaScript
• Disabling CSRF middleware instead of fixing token
• Sending token in URL query parameters