CVE-2010-3082 Cross-site scripting in django
Remote attackers can inject arbitrary web script or HTML via the csrfmiddlewaretoken cookie in Django, requiring user interaction to execute.
- 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
What is CVE-2010-3082?
CVE-2010-3082 is a medium-severity cross-site scripting vulnerability in Djangoproject Django, published on 14 Sep 2010. 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
Cross-site scripting (XSS) vulnerability in Django 1.2.x before 1.2.2 allows remote attackers to inject arbitrary web script or HTML via a csrfmiddlewaretoken (aka csrf_token) cookie.
Weakness: CWE-79
Which versions are affected by CVE-2010-3082?
3 open source packages ship an affected version, including django and Django. It affects 1 product.
| Package | Affected | Fixed in |
|---|---|---|
django PyPI | From 1.2 | 1.2.2 |
django PyPI | From 1.2 | 1.2.2 |
Django PyPI | From 1.2 | 1.2.2 |
Products include Djangoproject Django.
How do I fix CVE-2010-3082?
Upgrade django to 1.2.2 or later.
Escape output for the context it lands in and set a strict Content Security Policy. Upgrading the affected component is the real fix. More about Cross-site scripting.
Is CVE-2010-3082 being exploited?
There is no known exploitation of CVE-2010-3082 in the wild and no public exploit code.
Other vulnerabilities in Djangoproject Django
- CVE-2026-4277 Privilege abuse in GenericInlineModelAdmin
- CVE-2024-53908 Django SQL injection in HasKey(lhs, rhs) on Oracle
- CVE-2024-42005 Django SQL injection vulnerability
- CVE-2023-31047 Django bypasses validation when using one form field to upload multiple files
- CVE-2022-34265 Django `Trunc()` and `Extract()` database functions vulnerable to SQL Injection
Sources
Also known as DEBIAN-CVE-2010-3082, GHSA-fxpg-gg9g-76gj, PYSEC-2010-12.