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

> Remote attackers can perform cross-site request forgery to delete or modify data in the Django administration application by exploiting unauthenticated request storage.

- **Severity:** Medium 5.8 (`AV:N/AC:M/Au:N/C:N/I:P/A:P`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** Yes
- **Published:** 4 Sep 2008
- **Updated:** 7 Aug 2024
- **Also known as:** DEBIAN-CVE-2008-3909, GHSA-r5cj-wv24-92p5, PYSEC-2008-2

## 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 (Cross-Site Request Forgery)

## Which versions are affected by CVE-2008-3909?

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


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `django` | PyPI | All versions | 1.1 |
| `django` | PyPI | From 0.91.0 | 0.91.3 |
| `django` | PyPI | From 0.95.0 | 0.95.4 |
| `django` | PyPI | From 0.96.0 | 0.96.3 |
| `Django` | PyPI | From 0.91.0 | 0.91.3 |
| `Django` | PyPI | From 0.95.0 | 0.95.4 |
| `Django` | PyPI | From 0.96.0 | 0.96.3 |

Products: 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](https://insights.sbomify.com/CVE-2026-4277/): Privilege abuse in GenericInlineModelAdmin (critical 9.8)
- [CVE-2024-53908](https://insights.sbomify.com/CVE-2024-53908/): Django SQL injection in HasKey(lhs, rhs) on Oracle (critical 9.8)
- [CVE-2024-42005](https://insights.sbomify.com/CVE-2024-42005/): Django SQL injection vulnerability (critical 9.8)
- [CVE-2023-31047](https://insights.sbomify.com/CVE-2023-31047/): Django bypasses validation when using one form field to upload multiple files (critical 9.8)
- [CVE-2022-34265](https://insights.sbomify.com/CVE-2022-34265/): Django `Trunc()` and `Extract()` database functions vulnerable to SQL Injection (critical 9.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2008-3909 and fix it if it is affected.

What it is: 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.
Exploitation: There is no known exploitation of CVE-2008-3909 in the wild and no public exploit code.

Affected packages and fixed versions:
- django (PyPI): affected all versions; fixed in 1.1
- django (PyPI): affected from 0.91.0; fixed in 0.91.3
- django (PyPI): affected from 0.95.0; fixed in 0.95.4
- django (PyPI): affected from 0.96.0; fixed in 0.96.3
- Django (PyPI): affected from 0.91.0; fixed in 0.91.3
- Django (PyPI): affected from 0.95.0; fixed in 0.95.4
- Django (PyPI): affected from 0.96.0; fixed in 0.96.3

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2008-3909/ (Markdown: https://insights.sbomify.com/CVE-2008-3909/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2008-3909
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2008-3909
- OSV: https://osv.dev/vulnerability/CVE-2008-3909

---
From sbomify Insights: https://insights.sbomify.com/CVE-2008-3909/
Summaries are generated and may contain mistakes; the official description above is the record.