CVE-2011-4136

What it is

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.

At a glance

Exploitability

Can be exploited over the network without logging in. Limited direct impact.

Exploit odds

2.3% chance of exploitation in the next 30 days (EPSS).

Fix

A patch, advisory or fixed version is referenced. Upgrade or apply it.

Timeline

1. 2011-10-19 10:55 UTC PublishedDisclosed publicly on CVE.org and NVD
2. 2026-06-16 23:34 UTC Last updatedMost recent change to the record

Why it ranks here

• Exploited in the wild: no, CISA does not list it.
• Exploit odds: 2.3% in the next 30 days (EPSS).
• Severity: 5.8 MEDIUM (CVSS).
• Fix: a patch or advisory is linked.

Details

Published

2011-10-19 10:55 UTC

Last modified

2026-06-16 23:34 UTC

Exploit probability

2.3% · EPSS, next 30 days

Weakness

CWE-20 · Improper input validation

Record status

Modified

Affected

• Djangoproject Django ≤ 1.2.6
• Djangoproject Django 0.91
• Djangoproject Django 0.95
• Djangoproject Django 0.95.1
• Djangoproject Django 0.96
• Djangoproject Django 1.0
• Djangoproject Django 1.0.1
• Djangoproject Django 1.0.2

Attack profile CVSS 2.0 · 5.8

Attack vector

Network

Complexity

Medium

Authentication

None

Confidentiality

None

Integrity

Partial

Availability

Partial

Is it in your code?

Hand this to your coding agent. It searches your project for the affected products and checks versions. Nothing leaves your machine.

Read https://cve-list.com/agent/cve/CVE-2011-4136.md and follow it. Check whether this project is affected by CVE-2011-4136. Read only. Don't change anything and don't upload my code. Tell me yes, no or not sure, with the file as proof.

Copy as ticket · More options · Status badge