Skip to content
Noroxi
CVE-2018-6188· NVD / CVE Program· CNA mitre

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

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.

HighCVSS 7.5 · v3.0—No exploit Fix available

Noroxi analysis

No Noroxi analysis for this record yet

We don't hand-write analysis for the hundreds of thousands of vulnerabilities in the database; that wouldn't be honest. For notable, high-impact vulnerabilities our team writes the mechanism, detection and remediation steps.

We use this product, ask for help
Published
Feb 4, 2018
Updated
Jun 16, 2026
EPSS
4.8% · 92th percentile
Follow this CVE

Sign in to follow · You’ll be notified if a followed record enters KEV, gets an exploit or is updated.

Report tools

JSON

Action score

31

Monitor

Low priority for now.

CVSS
30 / 40 · 7.5 / 10
CISA KEV
0 / 30 · Not listed
EPSS
1 / 30 · 4.8%

Affected systems

VendorProduct
djangoprojectdjango
canonicalubuntu linux

Affected versions

NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.

  • canonical ubuntu linux17.10
  • djangoproject django1.11.8
  • djangoproject django1.11.9
  • djangoproject django2.0
  • djangoproject django2.0.1

Package-level exposure

OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.

EcosystemPackageAffected rangeFix
Alpine:v3.10py-djangobefore 1.11.10-r01.11.10-r0
Alpine:v3.11py3-djangobefore 1.11.10-r01.11.10-r0
Alpine:v3.6py-djangobefore 1.11.11-r01.11.11-r0
Debian:12python-djangobefore 1:1.11.10-11:1.11.10-1
openSUSE:Tumbleweedpython-Djangobefore 5.2.16-1.15.2.16-1.1
openSUSE:Tumbleweedpython-Djangobefore 3.2.7-2.33.2.7-2.3
openSUSE:Tumbleweedpython-Djangobefore 4.2.11-2.14.2.11-2.1
openSUSE:Tumbleweedpython-Django4before 4.2.30-4.14.2.30-4.1
openSUSE:Tumbleweedpython-Django4before 4.2.14-1.14.2.14-1.1
openSUSE:Tumbleweedpython-Django5before 5.2.16-1.15.2.16-1.1
openSUSE:Tumbleweedpython-Django6before 6.0-1.16.0-1.1
PyPIdjangofrom 1.11.8 · before 1.11.101.11.10
PyPIdjangofrom 2.0 · before 2.0.22.0.2
PyPIdjangofrom 2.0a1 · before 2.0.22.0.2
SUSE:Package Hub 12python-Djangobefore 1.11.10-5.11.11.10-5.1
SUSE:Package Hub 12 SP1python-Djangobefore 1.11.15-2.11.11.15-2.1

Other highest-scoring records for the same primary product.

  • CVE-2022-34265An issue was discovered in Django 3.2 before 3.2.14 and 4.0 before 4.0.6.
    61This week
  • CVE-2020-7471Django 1.11 before 1.11.28, 2.2 before 2.2.10, and 3.0 before 3.0.3 allows SQL Injection if untrusted data is used as a StringAgg delimiter
    59Plan
  • CVE-2019-19844Django before 1.11.27, 2.x before 2.2.9, and 3.x before 3.0.1 allows account takeover.
    55Plan
  • CVE-2019-14234An issue was discovered in Django 1.11.x before 1.11.23, 2.1.x before 2.1.11, and 2.2.x before 2.2.4.
    53Plan
  • CVE-2021-35042Django 3.1.x before 3.1.13 and 3.2.x before 3.2.5 allows QuerySet.order_by SQL injection if order_by is untrusted input from a client of a w
    52Plan
  • CVE-2023-24580An issue was discovered in the Multipart Request Parser in Django 3.2 before 3.2.18, 4.0 before 4.0.10, and 4.1 before 4.1.7.
    49Plan

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

Product / packageFixed versionSource
alpine:py-django1.11.10-r0 · Alpine:v3.10Package registry (OSV)
alpine:py3-django1.11.10-r0 · Alpine:v3.11Package registry (OSV)
debian:python-django1:1.11.10-1 · Debian:12Package registry (OSV)
opensuse:python-Django3.2.7-2.3 · openSUSE:TumbleweedPackage registry (OSV)
opensuse:python-Django44.2.14-1.1 · openSUSE:TumbleweedPackage registry (OSV)
opensuse:python-Django55.2.16-1.1 · openSUSE:TumbleweedPackage registry (OSV)
opensuse:python-Django66.0-1.1 · openSUSE:TumbleweedPackage registry (OSV)
PyPI:django1.11.10Package registry (OSV)
PyPI:django2.0.2Package registry (OSV)
suse:python-Django1.11.10-5.1 · SUSE:Package Hub 12Package registry (OSV)

Exploit status

No known public exploit

No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.

Research context

For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.

Timeline

From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.

No dated events beyond publication.

EPSS, last 120 days+1% in 7 days

FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).

Patch and commit links

Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.

No commit or PR link among the references.

Finders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.

No credits in the CNA record.

Variant candidates

Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.

No nightly-computed relations.

Chain candidates

An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.

—

Bug bounty scope

No known public program.

Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).

Technical details

Attack conditions

  • Anyone who can reach it over the internet can trigger it.
  • No account or password is required.
  • No user action is required.
  • No special conditions are required; it is repeatable.

If successful

Confidentiality
high · data can be read
Integrity
none
Availability
none
Attack vector
Network
Attack complexity
Low
Privileges required
None
User interaction
None
Scope
Unchanged
Confidentiality impact
High
Integrity impact
None
Availability impact
None

CVSS vector

CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N

nvd-primary

Root cause

The extension requests broader permissions than its function needs and sends the data it collects out for purposes beyond its stated function.

A representative example of this vulnerability class. Not the vendor's source code; it shows the faulty pattern and its fix.

Vulnerable

json
{  "permissions": ["tabs", "<all_urls>"],  "background": { "service_worker": "analytics.js" }}

Fixed

json
{  "permissions": ["activeTab"],  "host_permissions": ["https://yildiz.example/*"]}

Change log

  1. Fix✗ → ✓

For records you follow, these changes also arrive as notifications. →

References

Vendor advisories and official records. Exploit/PoC links are deliberately left out.

All records