CVE-2010-4534: Django - Improper Restriction of Query String to Perform Object Filtering
Summary
CVE-2010-4534: 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 a... Affects django across 2 version ranges.
< 1.1.3
>= 1.2, < 1.2.4
Fixed in 1.1.3 or 1.2.4, depending on the release line you run. How to fix ↓
Also tracked for
- python-django · Debian:11
The same CVE-2010-4534 is tracked separately for each ecosystem and vendor. Its fix information is the same; the package and affected versions differ.
Check if this vulnerability affects your application
Upload a manifest or SBOM and we'll show whether you're affected, plus every other risky package in the same scan.
No signup required · Results in about 60 seconds
Background
Django is a popular Python web framework that provides a high-level development environment for building web applications. It includes various components and modules to simplify common web development tasks. One of these components is the administrative interface (django.contrib.admin), which allows authorized users to manage and interact with the application's data models. However, prior to versions 1.1.3, 1.2.x before 1.2.4, and 1.3.x before 1.3 beta 1, Django's administrative interface had a vulnerability that could be exploited by remote authenticated users.
Vulnerability Detail
The vulnerability in Django's administrative interface arises from improper restriction of the use of query strings for object filtering. This means that remote authenticated users could manipulate the query string parameters to obtain sensitive information from the application. By crafting a series of requests containing regular expressions, an attacker could exploit the 'created_by__password__regex' parameter to retrieve sensitive data. This could potentially lead to unauthorized access, data leakage, or other security breaches.
How To Fix
Latest published version: 6.1.2 as of 22 Oct 2026
pip install --upgrade "django==6.1.2"
Upgrading to it may include breaking changes; the versions below are the minimum fixed release for this vulnerability.
If you can't move to the latest
The minimum fixed version depends on the release line you run.
-
< 1.1.31.1.3pip install --upgrade "django==1.1.3" -
>= 1.2, < 1.2.41.2.4pip install --upgrade "django==1.2.4"
Tip — Not sure which release line you're on? Vulert can find the fix for the version you are using. Scan free →
Workaround
As a workaround, users can manually apply a patch or modify the affected code to address the vulnerability. However, it is strongly recommended to upgrade to the fixed versions mentioned above, as manual modifications may introduce errors or compatibility issues. Here is an example of a patch that addresses the vulnerability:
# Apply this patch to the affected code
from django.contrib.admin.views.main import ChangeList
def get_query_string(self, new_params=None, remove=None):
if new_params is None:
new_params = {}
if remove is None:
remove = []
params = self.params.copy()
for r in remove:
for k in list(params):
if k.startswith(r):
del params[k]
params.update(new_params)
return '?' + '&'.join([f'{k}={v}' for k, v in params.items()])
ChangeList.get_query_string = get_query_string
Applying this patch modifies the 'get_query_string' method in the 'ChangeList' class of the 'django.contrib.admin.views.main' module to properly handle query string parameters and prevent the vulnerability.
Conclusion
In conclusion, the vulnerability in Django's administrative interface allows remote authenticated users to obtain sensitive information by manipulating query string parameters. To mitigate this vulnerability, it is crucial to upgrade to the fixed versions (1.1.3 or later, 1.2.4 or later, or 1.3 beta 1 or later) or apply the provided patch. For further support on vulnerability remediation, please contact DevNack.com.
See every vulnerability recorded for django →
FAQ
The vulnerability allows remote authenticated users to obtain sensitive information from the application. This could lead to unauthorized access, data leakage, or other security breaches.
Users of Django versions before 1.1.3, 1.2.x before 1.2.4, and 1.3.x before 1.3 beta 1 are affected by this vulnerability. If you are using an affected version and have the administrative interface enabled, you may be vulnerable.
You can use Vulert's playground at Vulert Scanner to check if your application is affected by this vulnerability. Vulert monitors and alerts in real-time for open-source vulnerabilities, using just the Pipfile.lock file.
While specific exploits for this vulnerability are not mentioned, it is important to address the vulnerability promptly by upgrading to the fixed versions or applying the provided patch. This helps mitigate the risk of potential exploitation.
You can find more information about this vulnerability in the Django advisory database at https://github.com/pypa/advisory-database/blob/main/vulns/django/PYSEC-2011-8.yaml
Related vulnerabilities
Recent vulnerabilities recorded for django.