CVE-2018-16984

What it is

An issue was discovered in Django 2.1 before 2.1.2, in which unprivileged users can read the password hashes of arbitrary accounts. The read-only password widget used by the Django Admin to display an obfuscated password hash was bypassed if a user has only the "view" permission (new in Django 2.1), resulting in display of the entire password hash to those users. This may result in a vulnerability for sites with legacy user accounts using insecure hashes.

At a glance

Exploitability

Can be exploited over the network with an admin-level account. High risk of data exposure.

Exploit odds

2.1% chance of exploitation in the next 30 days (EPSS).

Fix

A patch, advisory or fixed version is referenced. Upgrade or apply it.

Timeline

1. 2018-10-02 18:29 UTC PublishedDisclosed publicly on CVE.org and NVD
2. 2026-06-17 01:45 UTC Last updatedMost recent change to the record

Why it ranks here

• Exploited in the wild: no, CISA does not list it.
• Exploit odds: 2.1% in the next 30 days (EPSS).
• Severity: 4.9 MEDIUM (CVSS).
• Fix: a patch or advisory is linked.

Details

Published

2018-10-02 18:29 UTC

Last modified

2026-06-17 01:45 UTC

Exploit probability

2.1% · EPSS, next 30 days

Weakness

CWE-522

Record status

Modified

Affected

• Djangoproject Django < 2.1.2

Attack profile CVSS 3.0 · 4.9

Attack vector

Network

Complexity

Low

Privileges needed

High

User interaction

None

Scope

Unchanged

Confidentiality

High

Integrity

None

Availability

None

Is it in your code?

Hand this to your coding agent. It searches your project for the affected products and checks versions. Nothing leaves your machine.

Read https://cve-list.com/agent/cve/CVE-2018-16984.md and follow it. Check whether this project is affected by CVE-2018-16984. Read only. Don't change anything and don't upload my code. Tell me yes, no or not sure, with the file as proof.

Copy as ticket · More options · Status badge