Skip to content
Noroxi
CVE-2010-4534· NVD / CVE Program· CNA redhat

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 proper

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.

MediumCVSS 4.0 · v2.0—No exploit Fix available
Published
Jan 10, 2011
Updated
Jun 16, 2026
EPSS
2.5% · 84th percentile
Follow this CVE

Sign in to follow · You’ll be notified if a followed record enters KEV, gets an exploit or is updated.

Report tools

JSON

Action score

17

Monitor

Low priority for now.

CVSS
16 / 40 · 4.0 / 10
CISA KEV
0 / 30 · Not listed
EPSS
1 / 30 · 2.5%

Affected systems

VendorProduct
djangoprojectdjango

Affected versions

NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.

  • djangoproject djangoup to 1.1.2 inclusive
  • djangoproject django0.91
  • djangoproject django0.95
  • djangoproject django0.95.1
  • djangoproject django0.96
  • djangoproject django1.0
  • djangoproject django1.0.1
  • djangoproject django1.0.2
  • djangoproject django1.1
  • djangoproject django1.1.0
  • djangoproject django1.2
  • djangoproject django1.2.1
  • djangoproject django1.2.2
  • djangoproject django1.2.3
  • djangoproject django1.3

Package-level exposure

OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.

EcosystemPackageAffected rangeFix
Debian:12python-djangobefore 1.2.4-11.2.4-1
PyPIdjangofrom 1.2 · before 1.2.41.2.4
PyPIdjangobefore 1.1.31.1.3

Other highest-scoring records for the same primary product.

  • CVE-2022-34265An issue was discovered in Django 3.2 before 3.2.14 and 4.0 before 4.0.6.
    61This week
  • CVE-2020-7471Django 1.11 before 1.11.28, 2.2 before 2.2.10, and 3.0 before 3.0.3 allows SQL Injection if untrusted data is used as a StringAgg delimiter
    59Plan
  • CVE-2019-19844Django before 1.11.27, 2.x before 2.2.9, and 3.x before 3.0.1 allows account takeover.
    55Plan
  • CVE-2019-14234An issue was discovered in Django 1.11.x before 1.11.23, 2.1.x before 2.1.11, and 2.2.x before 2.2.4.
    53Plan
  • CVE-2021-35042Django 3.1.x before 3.1.13 and 3.2.x before 3.2.5 allows QuerySet.order_by SQL injection if order_by is untrusted input from a client of a w
    52Plan
  • CVE-2023-24580An issue was discovered in the Multipart Request Parser in Django 3.2 before 3.2.18, 4.0 before 4.0.10, and 4.1 before 4.1.7.
    49Plan

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

Product / packageFixed versionSource
debian:python-django1.2.4-1 · Debian:12Package registry (OSV)
PyPI:django1.1.3Package registry (OSV)
PyPI:django1.2.4Package registry (OSV)

Exploit status

No known public exploit

No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.

Research context

For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.

Timeline

From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.

No dated events beyond publication.

EPSS, last 120 days+1% in 7 days

FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).

Patch and commit links

Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.

Finders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.

No credits in the CNA record.

Variant candidates

Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.

No nightly-computed relations.

Chain candidates

An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.

—

Bug bounty scope

No known public program.

Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).

Technical details

Attack conditions

  • No special conditions are required; it is repeatable.

If successful

Confidentiality
P · data can be read
Integrity
none
Availability
none
Attack complexity
Low
Confidentiality impact
P
Integrity impact
None
Availability impact
None

CVSS vector

AV:N/AC:L/Au:S/C:P/I:N/A:N

nvd-primary

Attack context

MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.

MITRE has no CAPEC/ATT&CK mapping for this CWE.

Noroxi analysis

No Noroxi analysis for this record yet

We don't hand-write analysis for all 385,000+ vulnerabilities; that wouldn't be honest. For notable, high-impact vulnerabilities our team writes the mechanism, detection and remediation steps.

We use this product, ask for help

Change log

  1. Fix✗ → ✓

For records you follow, these changes also arrive as notifications. →

References

All records