All reports
Low

django: Password hash disclosure to "view only" admin users with custom user models

Affected versions

Affected versions
Unknown
Fixed version
Not reported
Affected versions
Unknown
Fixed version
Not reported
Affected versions
Unknown
Fixed version
Not reported
Affected versions
Unknown
Fixed version
Not reported
Affected versions
Unknown
Fixed version
Not reported
Affected versions
Unknown
Fixed version
Not reported
Affected versions
Unknown
Fixed version
Not reported
Affected versions
Unknown
Fixed version
Not reported

Exploitation

CVE-2026-113733

Probability of exploitation in the next 30 days: 0.39%

FIRST EPSS · 2026-11-21

Description

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.

A flaw was found in Django. Administrative users granted view-only permissions to user accounts may be exposed to full password hashes when viewing specific custom user models. In certain configurations involving custom or inherited user account structures, the administrative interface improperly displays the complete password hash instead of masking or withholding it. This information disclosure allows users with read-only administrative access to retrieve sensitive credential hashes, potentially enabling offline password-cracking attacks.