CVE-2008-3909 Django cross-site request forgery (CSRF) vulnerability

What is CVE-2008-3909?

CVE-2008-3909 is a medium-severity vulnerability in Djangoproject Django, published on 4 Sep 2008. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

Official description

The administration application in Django 0.91, 0.95, and 0.96 stores unauthenticated HTTP POST requests and processes them after successful authentication occurs, which allows remote attackers to conduct cross-site request forgery (CSRF) attacks and delete or modify data via unspecified requests.

Weakness: CWE-352

Which versions are affected by CVE-2008-3909?

7 open source packages ship an affected version, including django and Django. It affects 1 product.

Products include Djangoproject Django.

How do I fix CVE-2008-3909?

Upgrade django to a fixed version for your release line: 1.1, 0.91.3, 0.95.4 or 0.96.3.

Is CVE-2008-3909 being exploited?

There is no known exploitation of CVE-2008-3909 in the wild and no public exploit code.

Other vulnerabilities in Djangoproject Django

• CVE-2026-4277 Privilege abuse in GenericInlineModelAdmin Critical 9.8
• CVE-2024-53908 Django SQL injection in HasKey(lhs, rhs) on Oracle Critical 9.8
• CVE-2024-42005 Django SQL injection vulnerability Critical 9.8
• CVE-2023-31047 Django bypasses validation when using one form field to upload multiple files Critical 9.8
• CVE-2022-34265 Django `Trunc()` and `Extract()` database functions vulnerable to SQL Injection Critical 9.8

All Djangoproject Django vulnerabilities

Sources

• CVE record
• NVD
• OSV
• GitHub advisory
• How this page is made

Also known as DEBIAN-CVE-2008-3909, GHSA-r5cj-wv24-92p5, PYSEC-2008-2.