CVE-2014-0483 Django data leakage via querystring manipulation in admin

What is CVE-2014-0483?

CVE-2014-0483 is a low-severity vulnerability in Djangoproject Django, published on 26 Aug 2014. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.

Official description

The administrative interface (contrib.admin) in Django before 1.4.14, 1.5.x before 1.5.9, 1.6.x before 1.6.6, and 1.7 before release candidate 3 does not check if a field represents a relationship between models, which allows remote authenticated users to obtain sensitive information via a to_field parameter in a popup action to an admin change form page, as demonstrated by a /admin/auth/user/?pop=1&t=password URI.

Weakness: CWE-264

Which versions are affected by CVE-2014-0483?

9 open source packages ship an affected version, including django and Django. It affects 2 products.

Products include Djangoproject Django, Opensuse Opensuse.

How do I fix CVE-2014-0483?

Upgrade django to a fixed version for your release line: 1.4.14, 1.5.9, 1.6.6 or 1.7c3.

Is CVE-2014-0483 being exploited?

There is no known exploitation of CVE-2014-0483 in the wild and no public exploit code.

Other vulnerabilities in Djangoproject Django

• CVE-2026-4277 Privilege abuse in GenericInlineModelAdmin Critical 9.8
• CVE-2024-53908 Django SQL injection in HasKey(lhs, rhs) on Oracle Critical 9.8
• CVE-2024-42005 Django SQL injection vulnerability Critical 9.8
• CVE-2023-31047 Django bypasses validation when using one form field to upload multiple files Critical 9.8
• CVE-2022-34265 Django `Trunc()` and `Extract()` database functions vulnerable to SQL Injection Critical 9.8

All Djangoproject Django vulnerabilities

Sources

• CVE record
• NVD
• OSV
• GitHub advisory
• How this page is made

Also known as DEBIAN-CVE-2014-0483, GHSA-rw75-m7gp-92m3, PYSEC-2014-7, UBUNTU-CVE-2014-0483.