Skip to content
Fencer Intel
medium 6.5

CVE-2010-4534 json

Improper query string handling in Django

published 2011-01-10 15 y ago modified 2026-06-28 4 mo ago also GHSA-fwr5-q9rx-294f , PYSEC-2011-28 , PYSEC-2011-8 , EUVD-2011-0011

cvss
6.5
version 3.1, GitHub
cisa kev
Not listed
not in CISA's catalog
epss
2.5%
EPSS 2.5% chance of exploitation in 30 days, percentile 84%
public exploits
0
none known

Summary

The administrative interface in django.contrib.admin in Django before 1.1.3, 1.2.x before 1.2.4, and 1.3.x before 1.3 beta 1 does not properly restrict use of the query string to perform certain object filtering, which allows remote authenticated users to obtain sensitive information via a series of requests containing regular expressions, as demonstrated by a created_by__password__regex parameter.

Patch / fix

  • pypi django 1.1.3, 1.2.4
  • python-django Debian 14, Debian 13, Debian 12 1.2.4-1

debian advisories DEBIAN-CVE-2010-4534

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-2010-4534 updated cvss 5.0

, CVE-2010-4535 Information leakage and DoS vulnerabilities in Django < 1.2.4 & 1.1.3

  • Red Hat All currently supported Red Hat products
    not 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.48% chance of exploitation in the next 30 days, higher than 84% of all scored CVEs (FIRST EPSS, 2026-11-09).

Exploits and checks

  • ngenuity-is.com http://ngenuity-is.com/advisories/2010/dec/22/information-leakage-in-django-administrative-inter/ referenced PoC, tagged "exploit" by a source, unverified
  • evilpacket.net http://evilpacket.net/2010/dec/22/information-leakage-django-administrative-interfac/ referenced PoC, tagged "exploit" by a source, unverified
  • archives.neohapsis.com http://archives.neohapsis.com/archives/fulldisclosure/2010-12/0580.html referenced PoC, tagged "exploit" by a source, unverified

CVSS scores

assigned by version score vector
NVD 2.0 4.0 AV:N/AC:L/Au:S/C:P/I:N/A:N
GitHub 3.1 6.5 CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N

Affected packages

ecosystem package affected fixed in
pypi django
<1.1.3
>=1.2, <1.2.4
1.1.3
1.2.4

Classification

Weakness
  • CWE-264 Permissions, Privileges, and Access Controls
  • CWE-20 Improper Input Validation
Technology feeds

References

Sources

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.