CVE-2019-16766

CVE-2019-16766 is a high-severity vulnerability in Labdigital Wagtail-2fa with a CVSS 3.x base score of 8.7. It is not currently listed as actively exploited by CISA, and its EPSS exploit-prediction score is low. The underlying weakness is classified as CWE-290.

Key facts

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.

Frequently asked questions

What is CVE-2019-16766?
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.
How severe is CVE-2019-16766?
CVE-2019-16766 has a CVSS 3.x base score of 8.7, rated high severity. It is exploitable over network with low attack complexity, requires high privileges and no user interaction. Impact on confidentiality is high, integrity high, and availability none.
Is CVE-2019-16766 being actively exploited?
It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 1% (63rd percentile), an estimate of the probability of exploitation in the next 30 days.
What products are affected by CVE-2019-16766?
CVE-2019-16766 affects Labdigital Wagtail-2fa. See the affected-products list for the exact vulnerable versions.
How do I fix CVE-2019-16766?
Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround. Given its high severity, prioritise patching exposed systems.
When was CVE-2019-16766 published?
CVE-2019-16766 was published on 2019-11-29 and last updated on 2026-06-17.

References

Affected products (1)

More vulnerabilities in Labdigital Wagtail-2fa

All CVEs affecting Labdigital Wagtail-2fa →

Other CWE-290 vulnerabilities

Browse all CWE-290 vulnerabilities →