CVE-2019-16766: Vulnerability in wagtail-2fa Allows Bypassing 2FA Check

wagtail-2fa Updated 02 Oct 2025

Summary

29/11/2019
Yes i
Moderate
8.7

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. Affects wagtail-2fa across 3 version ranges.

< 1.3.0 < 13b12995d35b566df08a17257a23863ab6efb0ca < a6711b29711729005770ff481b22675b35ff5c81

Fixed in 13b12995d35b566df08a17257a23863ab6efb0ca. How to fix ↓

Free scan

Check if this vulnerability affects your application

Upload a manifest or SBOM and we'll show whether you're affected, plus every other risky package in the same scan.

Check my app free

No signup required · Results in about 60 seconds

Upload your dependency manifest or SBOM

Drag & drop your file here or

Java Javascript PHP Python Go Rust Ruby Dart C/C++ Elixir CycloneDX SPDX

Upload a supported dependency manifest or SBOM. No installation or source-code access required.

See supported files and SBOM formats
SBOM sbom.json · bom.json · bom.xml · *.spdx.json · *.cdx.json · *.cdx.xml
Java pom.xml · gradle.lockfile · buildscript-gradle.lockfile
Javascript package-lock.json · yarn.lock · pnpm-lock.yaml
PHP composer.lock
Python poetry.lock · requirements.txt · Pipfile.lock
Go go.mod
Rust Cargo.lock
Ruby Gemfile.lock
Dart pubspec.lock
C/C++ conan.lock
Elixir mix.lock
Enter your work email to receive your report link.

Verify your email to view the full report and start 30 days of continuous monitoring. No credit card required.

Sponsored Devnack Penetration testing for web, API and mobile Manual testing by engineers who build software, not an auditor's checklist. Trusted by teams at Swift and Google Talk to Devnack

Background

wagtail-2fa is a package available on PyPI that provides two-factor authentication (2FA) functionality for the Wagtail CMS. It adds an extra layer of security to the login process by requiring users to provide a second form of authentication, in addition to their credentials, to access the CMS. This package is widely used by Wagtail CMS users to enhance the security of their websites.

Vulnerability Detail

The vulnerability identified as CVE-2019-16766 in wagtail-2fa allows an attacker who gains access to someone's Wagtail login credentials to bypass the 2FA check and gain unauthorized access to the CMS. By changing the URL after logging in with the stolen credentials, the attacker can bypass the 2FA verification process. Once inside the CMS, the attacker can add a new device and gain full access to the CMS, potentially compromising sensitive information and performing malicious actions. This vulnerability was patched in version 1.3.0 of wagtail-2fa.

How To Fix

Latest published version: 1.8.0 as of 22 Oct 2026

pip install --upgrade "wagtail-2fa==1.8.0"

Upgrading to it may include breaking changes; the version below is the minimum fixed release for this vulnerability.

If you need the minimum change

13b12995d35b566df08a17257a23863ab6efb0ca

This is the first release that contains the fix.

pip install --upgrade "wagtail-2fa==13b12995d35b566df08a17257a23863ab6efb0ca"

Tip — Not sure which version your app runs? Vulert can match this fix to it. Scan free →

Conclusion

The vulnerability in wagtail-2fa (CVE-2019-16766) allows an attacker with stolen login credentials to bypass the 2FA check and gain unauthorized access to the CMS. To mitigate this vulnerability, users should upgrade to version 1.3.0 or later of wagtail-2fa. This update includes the necessary security patches to prevent the bypass of the 2FA check. For further support on vulnerability remediation, please contact DevNack.com.

See every vulnerability recorded for wagtail-2fa →

Share this vulnerability

FAQ

wagtail-2fa is a package that provides two-factor authentication functionality for the Wagtail CMS, adding an extra layer of security to the login process.

The vulnerability allows an attacker with stolen login credentials to bypass the 2FA check by changing the URL after logging in. This grants the attacker unauthorized access to the CMS.

By bypassing the 2FA check, the attacker can add a new device and gain full access to the CMS. This can lead to unauthorized access to sensitive information and potential malicious actions.

Yes, the vulnerability has been patched in version 1.3.0 of wagtail-2fa. Users are advised to upgrade to this version or later to ensure they are protected.

To update wagtail-2fa to the latest version, run the command 'pip install --upgrade wagtail-2fa'. This will install the latest version of the package with the necessary security patches.

Related vulnerabilities

Recent vulnerabilities recorded for wagtail-2fa.

How To Fix

Latest published version: 1.8.0 as of 22 Oct 2026

pip install --upgrade "wagtail-2fa==1.8.0"

Upgrading to it may include breaking changes; the version below is the minimum fixed release for this vulnerability.

If you need the minimum change

13b12995d35b566df08a17257a23863ab6efb0ca

This is the first release that contains the fix.

pip install --upgrade "wagtail-2fa==13b12995d35b566df08a17257a23863ab6efb0ca"

Tip — Not sure which version your app runs? Vulert can match this fix to it. Scan free →

Subscribe to Vulert on Telegram
Daily digest of new CVEs, critical and high severity, affected packages and fixes — plus a weekly roundup.
Join the channel →
Help improve this record
Report an issue or send feedback