CVE-2019-16766

What it is

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.

At a glance

Exploitability

Can be exploited over the network with an admin-level account. High risk of data exposure, data tampering.

Exploit odds

1.5% chance of exploitation in the next 30 days (EPSS).

Fix

A patch, advisory or fixed version is referenced. Upgrade or apply it.

Timeline

1. 2019-11-29 17:15 UTC PublishedDisclosed publicly on CVE.org and NVD
2. 2026-06-17 02:22 UTC Last updatedMost recent change to the record

Why it ranks here

• Exploited in the wild: no, CISA does not list it.
• Exploit odds: 1.5% in the next 30 days (EPSS).
• Severity: 8.7 HIGH (CVSS).
• Fix: a patch or advisory is linked.

Details

Published

2019-11-29 17:15 UTC

Last modified

2026-06-17 02:22 UTC

Exploit probability

1.5% · EPSS, next 30 days

Weakness

CWE-290

Record status

Modified

Affected

• Labdigital wagtail-2fa < 1.3.0

Attack profile CVSS 3.1 · 8.7

Attack vector

Network

Complexity

Low

Privileges needed

High

User interaction

None

Scope

Changed

Confidentiality

High

Integrity

High

Availability

None

Is it in your code?

Hand this to your coding agent. It searches your project for the affected products and checks versions. Nothing leaves your machine.

Read https://cve-list.com/agent/cve/CVE-2019-16766.md and follow it. Check whether this project is affected by CVE-2019-16766. Read only. Don't change anything and don't upload my code. Tell me yes, no or not sure, with the file as proof.

Copy as ticket · More options · Status badge