CVE-2019-16766

Description

When using wagtail-2fa before 1.3.0, if someone gains access to someone's Wagtail login credentials, they can log into the CMS and bypass the 2FA check by changing the URL. They can then add a new device and gain full access to the CMS. This problem has been patched in version 1.3.0.

Severity
HIGH
CVSS v3
8.7
CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:C/C:H/I:H/A:N · source cna
Exploit chance (EPSS)
1.462%
chance of exploitation in the next 30 days
higher than 74% of scored CVEs · 2026-11-17
CISA KEV
Not listed
Public exploit code
None public
Exploit references (NVD and CNA): 0
Metasploit modules: 0
Nuclei templates: 0

Weakness

Timeline

  1. 2019-11-29Published by the CNA17:05 UTC
  2. 2019-11-29GitHub advisory published (GHSA-89px-ww3j-g2mm)same day

The timeline shows what already happened. To be told when this CVE changes next, watch it from the API.

Exploit and advisory records

GitHub advisory GHSA-89px-ww3j-g2mm, affected packages:

PackageVulnerable versionsFixed in
PyPI wagtail-2fabefore 1.3.01.3.0

Affected products

Products listed as vulnerable. Upgrade to the version under "Fixed in", or a later one.

ProductVulnerable versionsFixed in
labdigital wagtail-2fabefore 1.3.0fixed in 1.3.01.3.0

Products and versions as NVD and the vendor that published the CVE list them.

References

Get more CVE data from the API.

Free without a key or signup. Pro adds monitoring and higher limits: pricing.

Sources