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.
{ "github_reviewed": true, "nvd_published_at": null, "severity": "HIGH", "cwe_ids": [ "CWE-352" ], "github_reviewed_at": "2020-06-16T21:39:45Z" }