djangoproject Django up to 6.0.9/6.1.2 Admin Utils utils.py django.contrib.admin.utils.display_for_field information disclosure

Summaryinfo

A vulnerability was found in djangoproject Django up to 6.0.9/6.1.2. It has been classified as problematic. Impacted is the function django.contrib.admin.utils.display_for_field of the file django/contrib/admin/utils.py of the component Admin Utils. This manipulation causes information disclosure. This vulnerability is registered as CVE-2026-113733. Remote exploitation of the attack is possible. No exploit is available. Upgrading the affected component is recommended.

Detailsinfo

A vulnerability classified as problematic was found in djangoproject Django up to 6.0.9/6.1.2. Affected by this vulnerability is the function django.contrib.admin.utils.display_for_field of the file django/contrib/admin/utils.py of the component Admin Utils. The manipulation with an unknown input leads to a information disclosure vulnerability. The CWE definition for the vulnerability is CWE-200. The product exposes sensitive information to an actor that is not explicitly authorized to have access to that information. As an impact it is known to affect confidentiality. The summary by CVE is:

An issue was discovered in Django 6.1 before 6.1.3 and 6.0 before 6.0.10. The `django.contrib.admin.utils.display_for_field()` function did not obfuscate the password field of user models other than `AUTH_USER_MODEL`, or of an `AUTH_USER_MODEL` inheriting its password field from a concrete parent model through multi-table inheritance, which allows authenticated staff users with only the view permission on such a model to obtain full password hashes via the read-only change form. Earlier, unsupported Django series (such as 5.1.x, 5.0.x, and 4.2.x) were not evaluated and may also be affected. Django would like to thank Aaron chen for reporting this issue.

It is possible to read the advisory at docs.djangoproject.com. This vulnerability is known as CVE-2026-113733 since 10/20/2026. The exploitation appears to be easy. The attack can be launched remotely. Technical details of the vulnerability are known, but there is no available exploit. The pricing for an exploit might be around USD $0-$5k at the moment (estimation calculated on 11/03/2026). The attack technique deployed by this issue is T1592 according to MITRE ATT&CK.

Upgrading to version 6.0.10 or 6.1.3 eliminates this vulnerability.

Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.

Productinfo

Type

• Content Management System

Vendor

• djangoproject

Name

• Django

Version

• 6.0.0
• 6.0.1
• 6.0.2
• 6.0.3
• 6.0.4
• 6.0.5
• 6.0.6
• 6.0.7
• 6.0.8
• 6.0.9
• 6.1.0
• 6.1.1
• 6.1.2

License

• open-source

CPE 2.3info

• 🔒
• 🔒
• 🔒

CPE 2.2info

• 🔒
• 🔒
• 🔒

CVSSv4info

CVSSv3info

CVSSv2info

Exploitinginfo

Threat Intelligenceinfo

Countermeasuresinfo

Timelineinfo

Sourcesinfo

Entryinfo

Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.

Discussion