Django Project Django 2.0
Approved changes feed: RSS · Atom
cpe:2.3:a:djangoproject:django:2.0:*:*:*:*:*:*:*
part: a version: 2.0 update: *
| Vendor | Djangoproject (070db687-4713-5da4-80b0-4a67baf0d0d4) |
|---|---|
| Product | Django (b34a5fd0-fae8-5096-941f-bded7e4dd228) |
| Edition | * |
| Language | * |
| Software edition | * |
| Target software | * |
| Target hardware | * |
| Other | * |
| Notes | Imported from NVD CPE 2.0 feed |
PURL mappings
| PURL | Source | Last updated |
|---|---|---|
pkg:docker/django/django |
purl2cpe | 2026-06-01 10:17:26.828008 |
pkg:github/django/django |
purl2cpe | 2026-06-01 10:17:26.828010 |
pkg:pypi/django |
purl2cpe | 2026-06-01 10:17:26.828011 |
Vulnerability references
| Identifier | cpeApplicability | Submitted | db.gcve.eu details | Rationale |
|---|---|---|---|---|
CVE:CVE-2018-6188 |
vulnerable | 2026-06-08 05:11:53.429025 |
Details available
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.
Published: 2018-02-05T03:00:00.000Z
Updated: 2024-08-05T05:54:53.251Z |
Imported from gcve-enriched-dumps CVE data |
Contribute
You can submit an edit proposal for this CPE entry or suggest a related product/vendor addition using the action button above.