7.5
CWE
352
Advisory Published
Advisory Published
Updated

CVE-2011-4140: CSRF

First published: Wed Oct 19 2011(Updated: )

The CSRF protection mechanism in Django through 1.2.7 and 1.3.x through 1.3.1 does not properly handle web-server configurations supporting arbitrary HTTP Host headers, which allows remote attackers to trigger unauthenticated forged requests via vectors involving a DNS CNAME record and a web page containing JavaScript code.

Credit: cve@mitre.org cve@mitre.org

Affected SoftwareAffected VersionHow to fix
Djangoproject Django<=1.2.6
Djangoproject Django=1.2.5
Djangoproject Django=0.95
Djangoproject Django=1.0
Djangoproject Django=1.3
Djangoproject Django=1.1.2
Djangoproject Django=1.0.1
Djangoproject Django=1.1
Djangoproject Django=1.2.1
Djangoproject Django=1.2.4
Djangoproject Django=0.91
Djangoproject Django=1.0.2
Djangoproject Django=1.2.3
Djangoproject Django=1.3-alpha1
Djangoproject Django=1.1.3
Djangoproject Django=1.2.1-2
Djangoproject Django=1.2
Djangoproject Django=0.95.1
Djangoproject Django=0.96
Djangoproject Django=1.3-alpha2
Djangoproject Django=1.1.0
Djangoproject Django=1.2.2
pip/Django>=1.3<=1.3.1
pip/Django<=1.2.7

Never miss a vulnerability like this again

Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2025 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203