How severe is CVE-2019-16766?

CVE-2019-16766 has a CVSS score of 8.8/10, rated HIGH. Immediate patching is strongly recommended.

Which packages are affected by CVE-2019-16766?

CVE-2019-16766 affects the following packages: wagtail-2fa (PyPI). Ecosystems affected: PyPI.

How do I fix CVE-2019-16766?

Update wagtail-2fa to 1.3.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2019-16766 is resolved across your whole dependency graph.

How do I detect CVE-2019-16766 in my PyPI dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for wagtail-2fa, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate CVE-2019-16766 if there is no patch (or I can't update yet)?

If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

Is CVE-2019-16766 actively exploited in the wild?

No public exploit code has been indexed for CVE-2019-16766 yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

What is the EPSS score for CVE-2019-16766?

CVE-2019-16766 has an EPSS (Exploit Prediction Scoring System) score of 1.5%, placing it in the 74th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

What type of vulnerability is CVE-2019-16766?

CVE-2019-16766 is classified as CWE-290 (CWE-290), CWE-304 (CWE-304). These weakness types describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was CVE-2019-16766 published, and has it been updated?

CVE-2019-16766 was published on November 29, 2019 and was last updated on October 20, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

🐍

🐍 PyPI

Not in CISA KEV

HIGH severity

CVE-2019-16766 — wagtail-2fa

HIGHFix: labd/wagtail-2fa@13b1299

CVE-2019-16766 is a high-severity (CVSS 8.8) CWE-290 vulnerability in wagtail-2fa. A fix is available for wagtail-2fa — see the affected versions and patch details below.

2FA bypass in Wagtail through new device path

Also known asGHSA-89px-ww3j-g2mmPYSEC-2019-135

Published

Nov 29, 2019

Updated

Oct 20, 2026

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

Exploitation data as of Nov 6, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

EPSS Exploitation Probability

via FIRST.org ↗

1.5%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs74th percentile — riskier than 74% of all scored CVEsHighest risk

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

How urgent is this, really

Where this sits among everything scored

Real-World Exposure

1 pkg affected

🐍wagtail-2fa

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects PyPI packages — download data is not available via public APIs for these ecosystems.

Description

2FA bypass through new device path

Impact

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.

Patches

This problem has been patched in version 1.3.0.

Workarounds

There is no workaround at the moment.

For more information

If you have any questions or comments about this advisory:

Open an issue in github.com/labd/wagtail-2fa
Email us at [email protected]

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
🐍PyPI	`wagtail-2fa`	all versions	1.3.0`pip install --upgrade 'wagtail-2fa==1.3.0'`

Affected Products

1 product · 1 configurations

Application

wagtail-2falabdigital

< 1.3.0

range

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for wagtail-2fa, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update wagtail-2fa to 1.3.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2019-16766 is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

Frequently Asked Questions

## 2FA bypass through new device path ### Impact 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. ### Patches This problem has been patched in version 1.3.0. ### Workarounds There is no workaround at the moment. ### For more information If you have any questions or comments about this advisory: * Open an issue in [github.com/labd/wagtail-2fa](https://github.com/labd/wagtail-2fa) * Email us at [[email protected]](mailto:security@labdigit