CVE-2008-3909

CVE-2008-3909 is a medium-severity vulnerability in Djangoproject Django with a CVSS 2.0 base score of 5.8. It is not currently listed as actively exploited by CISA, and its EPSS exploit-prediction score is low. The underlying weakness is classified as CWE-352.

Key facts

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.

Frequently asked questions

What is CVE-2008-3909?
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.
How severe is CVE-2008-3909?
CVE-2008-3909 has a CVSS 2.0 base score of 5.8, rated medium severity.
Is CVE-2008-3909 being actively exploited?
It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 1% (56th percentile), an estimate of the probability of exploitation in the next 30 days.
What products are affected by CVE-2008-3909?
CVE-2008-3909 affects Djangoproject Django. See the affected-products list for the exact vulnerable versions.
How do I fix CVE-2008-3909?
Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround.
When was CVE-2008-3909 published?
CVE-2008-3909 was published on 2008-09-04 and last updated on 2026-06-16.

References

Affected products (1)

More vulnerabilities in Djangoproject Django

All CVEs affecting Djangoproject Django →

Other CWE-352 (Cross-Site Request Forgery (CSRF)) vulnerabilities

Browse all CWE-352 (Cross-Site Request Forgery (CSRF)) vulnerabilities →