CSRF protection concept in Flask

Introduction

CSRF protection stops bad websites from tricking you into doing things you don't want. It keeps your web app safe from sneaky attacks.

When you have forms that change data, like login or signup forms.

When users can update their profile or settings on your site.

When your app processes payments or sensitive actions.

When you want to keep user sessions secure from outside attacks.

Syntax

Flask

from flask import Flask
from flask_wtf import CSRFProtect

app = Flask(__name__)
app.config['SECRET_KEY'] = 'your-secret-key'
csrf = CSRFProtect(app)

You need to set a secret key for security.

CSRFProtect wraps your app to add protection automatically.

Examples

Basic setup to enable CSRF protection in a Flask app.

Flask

from flask import Flask
from flask_wtf import CSRFProtect

app = Flask(__name__)
app.config['SECRET_KEY'] = 'secret123'
csrf = CSRFProtect(app)

Example of a POST route that will be protected by CSRF automatically.

Flask

@app.route('/submit', methods=['POST'])
def submit():
    # Your form handling code here
    return 'Form submitted!'

In your HTML form, include form.hidden_tag() to add the CSRF token.

Flask

<form method="POST" action="/submit">
  {{ form.hidden_tag() }}
  <input type="text" name="name">
  <input type="submit" value="Send">
</form>

Sample Program

This Flask app shows a simple form with CSRF protection. The form includes a hidden CSRF token automatically. When you submit the form, it greets you by name.

Flask

from flask import Flask, render_template_string, request
from flask_wtf import FlaskForm, CSRFProtect
from wtforms import StringField, SubmitField

app = Flask(__name__)
app.config['SECRET_KEY'] = 'secret123'
csrf = CSRFProtect(app)

class NameForm(FlaskForm):
    name = StringField('Name')
    submit = SubmitField('Submit')

@app.route('/', methods=['GET', 'POST'])
def index():
    form = NameForm()
    if form.validate_on_submit():
        return f'Hello, {form.name.data}!'
    return render_template_string('''
        <form method="POST">
            {{ form.hidden_tag() }}
            {{ form.name.label }} {{ form.name() }}<br>
            {{ form.submit() }}
        </form>
    ''', form=form)

if __name__ == '__main__':
    app.run(debug=False)

Important Notes

Always set a strong secret key to keep tokens secure.

CSRF tokens are unique per user session and help verify requests are genuine.

Flask-WTF makes adding CSRF protection easy with forms.

Summary

CSRF protection stops attackers from tricking users into unwanted actions.

Use Flask-WTF's CSRFProtect and include tokens in your forms.

Always protect POST routes that change data.

Practice

1. What is the main purpose of CSRF protection in a Flask web application?

easy

A. To speed up the loading time of web pages

B. To encrypt user passwords in the database

C. To prevent attackers from making users perform unwanted actions without their consent

D. To improve the visual design of forms

Solution

1. Step 1: Understand what CSRF stands for

   CSRF means Cross-Site Request Forgery, which tricks users into submitting unwanted requests.

2. Step 2: Identify the purpose of CSRF protection

   CSRF protection stops attackers from forcing users to perform actions they did not intend.

3. Final Answer:

   To prevent attackers from making users perform unwanted actions without their consent -> Option C

4. Quick Check:

   CSRF protection = prevent unwanted user actions [OK]

Hint: CSRF stops fake actions from attackers using your login [OK]

Common Mistakes:

• Confusing CSRF with password encryption
• Thinking CSRF improves page speed
• Believing CSRF changes form appearance

2. Which of the following is the correct way to enable CSRF protection in a Flask app using Flask-WTF?

easy

A. from flask_wtf import CSRFProtect
app = Flask(__name__)
csrf = CSRFProtect(app)
csrf.init_app(app)

B. from flask_wtf import CSRFProtect
csrf = CSRFProtect()
app = Flask(__name__)

C. app = Flask(__name__)
app.csrf = True

D. from flask_wtf import CSRFProtect
csrf = CSRFProtect(app)

Solution

1. Step 1: Recall Flask-WTF CSRF setup

   You import CSRFProtect and pass the Flask app instance to it to enable protection.

2. Step 2: Check the options for correct syntax

   from flask_wtf import CSRFProtect csrf = CSRFProtect(app) correctly imports CSRFProtect and initializes it with the app in one step.

3. Final Answer:

   from flask_wtf import CSRFProtect csrf = CSRFProtect(app) -> Option D

4. Quick Check:

   CSRFProtect(app) initializes protection [OK]

Hint: Initialize CSRFProtect with app instance directly [OK]

Common Mistakes:

• Calling CSRFProtect without passing app
• Setting app.csrf = True (not valid)
• Calling init_app after passing app (redundant)

3. Given this Flask route with CSRF protection enabled, what happens if the form is submitted without a CSRF token?

@app.route('/submit', methods=['POST'])
def submit():
    return 'Success'

medium

A. The server raises a CSRF error and rejects the request

B. The server ignores the CSRF token and processes normally

C. The request is accepted and returns 'Success'

D. The server redirects to the home page without error

Solution

1. Step 1: Understand CSRF token role in POST requests

   CSRF tokens verify that the form submission is from a trusted source.

2. Step 2: Check behavior when token is missing

   Without a valid CSRF token, Flask-WTF raises an error and rejects the request.

3. Final Answer:

   The server raises a CSRF error and rejects the request -> Option A

4. Quick Check:

   Missing CSRF token = error rejection [OK]

Hint: POST without token triggers CSRF error [OK]

Common Mistakes:

• Assuming request is accepted without token
• Thinking server silently ignores missing token
• Believing server redirects instead of error

4. You added CSRF protection to your Flask app but get a 'CSRF token missing' error on form submission. Which fix will solve this issue?

medium

A. Add {{ form.csrf_token }} inside the HTML form

B. Remove the CSRFProtect initialization from the app

C. Change the form method to GET instead of POST

D. Disable CSRF protection in Flask-WTF config

Solution

1. Step 1: Identify cause of missing CSRF token

   The form must include the CSRF token field to send it with the request.

2. Step 2: Choose the fix that adds the token to the form

   Adding {{ form.csrf_token }} in the form template includes the token correctly.

3. Final Answer:

   Add {{ form.csrf_token }} inside the HTML form -> Option A

4. Quick Check:

   Include CSRF token in form to fix error [OK]

Hint: Always include {{ form.csrf_token }} in your forms [OK]

Common Mistakes:

• Removing CSRF protection instead of fixing token
• Changing POST to GET (not secure)
• Disabling CSRF protection globally

5. You want to protect a Flask route that updates user data via POST. Which combination correctly applies CSRF protection and form token usage?

hard

A. Use CSRFProtect(app) but omit the token in the form for simplicity

B. Enable CSRFProtect(app) and include {{ form.csrf_token }} in the HTML form

C. Skip CSRFProtect and rely on session cookies only

D. Add {{ form.csrf_token }} in form but do not enable CSRFProtect in app

Solution

1. Step 1: Understand CSRF protection requirements

   Both enabling CSRFProtect in the app and including the token in the form are needed to protect POST routes.

2. Step 2: Evaluate each option for completeness

   Only Enable CSRFProtect(app) and include {{ form.csrf_token }} in the HTML form correctly enables protection and includes the token in the form.

3. Final Answer:

   Enable CSRFProtect(app) and include {{ form.csrf_token }} in the HTML form -> Option B

4. Quick Check:

   Protect POST routes with CSRFProtect and token [OK]

Hint: Both app and form need CSRF setup for protection [OK]

Common Mistakes:

• Enabling protection but missing token in form
• Including token but not enabling protection
• Relying only on session cookies