CVE-2011-4136 json
Session manipulation in Django
published 2011-10-19 15 y ago modified 2026-06-16 4 mo ago also GHSA-x88j-93vc-wpmp , PYSEC-2011-1 , EUVD-2011-0003
- cvss
- 4.0
- version 3.1, GitHub
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 2.3%
- EPSS 2.3% chance of exploitation in 30 days, percentile 83%
- public exploits
- 0
- none known
Summary
django.contrib.sessions in Django before 1.2.7 and 1.3.x before 1.3.1, when session data is stored in the cache, uses the root namespace for both session identifiers and application-data keys, which allows remote attackers to modify a session by triggering use of a key that is equal to that session's identifier.
Patch / fix
- pypi django 1.2.7, 1.3.1
- python-django Debian 14, Debian 13, Debian 12 1.3.1-1
debian advisories DEBIAN-CVE-2011-4136
- github.com/django/django@ac7c3a1 commit
- github.com/django/django@fbe2eea commit
- bugzilla.redhat.com/show_bug.cgi?id=737366 patch
- openwall.com/lists/oss-security/2011/09/11/1 patch
- djangoproject.com/weblog/2011/sep/10/127/ patch
- openwall.com/lists/oss-security/2011/09/13/2 patch
- djangoproject.com/weblog/2011/sep/09/ advisory
Vendor advisories
What the vendors themselves say about their products: affected, fixed or not affected, and what to do.
red hat product security vex CVE-2011-4136 updated cvss 4.3
Django: v1.3.1, v1.2.7 multiple security flaws
-
Red Hat All currently supported Red Hat productsnot affected: vulnerable code not present
Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf
Exploit prediction
2.28% chance of exploitation in the next 30 days, higher than 83% of all scored CVEs (FIRST EPSS, 2026-11-09).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 2.0 | 5.8 | AV:N/AC:M/Au:N/C:N/I:P/A:P |
| GitHub | 3.1 | 4.0 | CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N |
Affected packages
| ecosystem | package | affected | fixed in |
|---|---|---|---|
| pypi | django | <1.2.7 >=1.3, <1.3.1 |
1.2.7 1.3.1 |
Classification
- Weakness
-
- CWE-20 Improper Input Validation
- Technology feeds
References
-
bugzilla.redhat.com
/show_bug.cgi?id=737366
web, patch, report
-
openwall.com
/lists/oss-security/2011/09/11/1
mailing-list, web, patch
-
djangoproject.com
/weblog/2011/sep/10/127/
patch, article
-
openwall.com
/lists/oss-security/2011/09/13/2
mailing-list, web, patch
-
djangoproject.com
/weblog/2011/sep/09/
patch, vendor-advisory, article
-
github.com
/django/django/commit/ac7c3a110f906e4dfed3a17451bf7fd9fcb81296
web
-
github.com
/django/django/commit/fbe2eead2fa9d808658ca582241bcacb02618840
web
-
hermes.opensuse.org
/messages/14700881
vendor-advisory, web
-
debian.org
/security/2011/dsa-2332
vendor-advisory, web, advisory
-
secunia.com
/advisories/46614
third-party-advisory, advisory
-
nvd.nist.gov
/vuln/detail/CVE-2011-4136
advisory
-
github.com
/advisories/GHSA-x88j-93vc-wpmp
advisory
-
github.com
/django/django
package
-
github.com
/pypa/advisory-database/tree/main/vulns/django/PYSEC-2011-1.yaml
web
-
djangoproject.com
/weblog/2011/sep/09
web
-
djangoproject.com
/weblog/2011/sep/10/127
web
Sources
- CVE List CVE-2011-4136
- GitHub Advisory GHSA-x88j-93vc-wpmp
- NVD CVE-2011-4136
- OSV PYSEC-2011-1
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.