How to fix: Django CSRF token cookie missing security attributes
The Django csrftoken cookie is present but may be missing Secure or SameSite attributes.
Why it matters
Without the Secure flag, the CSRF token is sent over HTTP connections where it can be intercepted. Without SameSite, it is sent on cross-site navigations, weakening CSRF protection.
Django's CSRF protection relies on the csrftoken cookie. If this cookie lacks Secure and SameSite attributes, an attacker can intercept or abuse it.
How to fix it
- 1Set CSRF_COOKIE_SECURE = True in Django settings
- 2Set CSRF_COOKIE_SAMESITE = "Strict" or "Lax"
- 3Set SESSION_COOKIE_SECURE = True and SESSION_COOKIE_SAMESITE = "Strict"
Code examples
settings.py: secure CSRF cookie
# settings.py
CSRF_COOKIE_SECURE = True
CSRF_COOKIE_SAMESITE = "Strict"
CSRF_COOKIE_HTTPONLY = True
SESSION_COOKIE_SECURE = True
SESSION_COOKIE_SAMESITE = "Strict"References
Detected automatically by VulnRadar. The check id is django-csrftoken-cookie-exposed, stable across every scan so you can filter or diff on it.
More info disclosure checks
- MediumRails Session Cookie Missing HttpOnly Flag
- InfoServer header truncated
- InfoPHP session cookie naming exposes runtime
- Infoconfig.js / settings.js referenced (verify contents)
- Infoenv.js / environment.js referenced (verify contents)
- InfoSitemap.xml publicly accessible
- InfoOpenAPI schema version exposed in URL
- LowCORS exposes internal CDN hostname
Questions
- How severe is Django CSRF token cookie missing security attributes?
- VulnRadar rates this medium severity in the info disclosure category. The severity is fixed per check, not scored per site, so the same finding is the same severity on every scan.
- Does VulnRadar check for this automatically?
- Yes. It runs as part of every scan under the check id django-csrftoken-cookie-exposed, which stays the same between runs so you can filter, diff, or gate CI on it.
- Which standards does Django CSRF token cookie missing security attributes map to?
- It maps to CWE-614. In the OWASP Top 10 it falls under A05:2021.
Missing a check?
The detection set is open. If you know a misconfiguration this does not catch, propose it: the issue template asks for the threat model, how to detect it, the false-positive risk, and a test fixture, which is the same thing a maintainer would have to work out anyway.