CVE-2019-16766: When using wagtail-2fa before 1.3.0, if someone gains access to someone's Wagtail login credentials, they can

Q: How do I fix CVE-2019-16766?

wagtail-2fa: upgrade to 1.3.0. Exact commands for each OS are on this page.

Q: Is CVE-2019-16766 being exploited?

CVE-2019-16766 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

Q: What does CVE-2019-16766 affect?

CVE-2019-16766 affects wagtail-2fa. Severity is high (CVSS 8.7). 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. Thi

This month

HIGH 8.7UPGRADE

CVE-2019-16766 is a high-severity flaw (CVSS 8.7) affecting wagtail-2fa. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

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.

Why this priority

High severity

A fixed release or distro patch exists.

Risk facts

CVSS score	8.7 (High)
Attack vector	Network (remote)
Attack complexity	Low
Privileges needed	High
User interaction	None
EPSS exploit chance	1.5% (top 26%)
CISA exploited list	No
Weakness	CWE-290, CWE-304
Published	2019-11-29
Last modified	2026-06-17

Publisher (CNA): GitHub, Inc. · Vendor: labdigital

Last updated 2026-06-17 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score

Am I affected?

Timeline

2019-11-29 17:15 UTCPublished CVE record published
2026-06-17 02:22 UTCUpdated Record last modified

labdigital wagtail-2fa UPGRADE

Affected: < 1.3.0

Fixed in: 1.3.0

Safe to downgrade to: no unaffected older release

1. Check installed version

apt-cache policy wagtail-2fa || rpm -q wagtail-2fa || wagtail-2fa --version

2. UPGRADE to 1.3.0 (Debian / Ubuntu)

sudo apt update && sudo apt install --only-upgrade wagtail-2fa

2. UPGRADE (RHEL / Amazon Linux / Fedora)

sudo dnf upgrade wagtail-2fa

Note

Distros often backport fixes without changing the version number. Confirm with the distro advisory or changelog.

Verify at the official source NVD · CVE Program · Report a problem with this page
Scores and fixes here are computed automatically from those and other public sources. Confirm with the vendor advisory before changing production systems.

Quick answers

How do I fix CVE-2019-16766?

wagtail-2fa: upgrade to 1.3.0. Exact commands for each OS are on this page.

Is CVE-2019-16766 being exploited?

CVE-2019-16766 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

What does CVE-2019-16766 affect?

CVE-2019-16766 affects wagtail-2fa. Severity is high (CVSS 8.7). 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. Thi

How urgent is CVE-2019-16766?

Priority 49/100. High severity

Related CVEs

CVE-2020-5240 HIGH 7.6 UPGRADE In wagtail-2fa before 1.4.1, any user with access to the CMS can view and delete other users 2FA devices by go

References

← Back to latest CVEs