# 2FA bypass in Wagtail through new device path

Advisory record · `GHSA-89px-ww3j-g2mm`

- **Identifiers:** `GHSA-89px-ww3j-g2mm` · `CVE-2019-16766` · `PYSEC-2019-135`
- **State:** Confirmed
- **Severity:** CVSS 8.7 High
- **Critical:** No
- **Weakness (CWE):** [CWE-290](https://cwe.mitre.org/data/definitions/290.html) · [CWE-304](https://cwe.mitre.org/data/definitions/304.html)
- **Tags:** [Authentication bypass](https://agentprime.io/advisories/tag/auth-bypass.md)
- **Published:** 29 Nov 2019
- **Updated:** 10 Sept 2026
- **Reviewed by a person:** No

Published by the GitHub Advisory Database at 29 Nov 2019, 17:05 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

## Affected packages

- `wagtail-2fa` (PyPI): affected `<1.3.0`; fixed in `1.3.0`

## Machine-written summary

Summary written by Claude Haiku from the source advisory. Not reviewed by a person.

> The wagtail-2fa package is vulnerable in versions before 1.3.0. An attacker who already has a user's Wagtail login credentials can bypass the two-factor authentication check by changing the URL, then add a new device and gain full access to the CMS. Upgrade to wagtail-2fa 1.3.0 or later; the source lists no workaround.

Written 5 Nov 2026.

## Not analysed yet

We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check.

## Severity and exploitation

- 8.7 High, CVSS 3.1: `CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:C/C:H/I:H/A:N`, from CNA (GitHub_M)

- **CISA KEV:** Not listed.
- **EPSS:** 0.015, the 74th percentile, on 21 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

## Timeline

- 31 Oct 2026, 14:37 UTC: First seen by agentprime
- 31 Oct 2026, 14:37 UTC: [Confirmed by OSV](https://osv.dev/vulnerability/GHSA-89px-ww3j-g2mm)

## Sources

- [GitHub Advisory Database: GHSA-89px-ww3j-g2mm](https://github.com/advisories/GHSA-89px-ww3j-g2mm)
- [OSV: GHSA-89px-ww3j-g2mm](https://osv.dev/vulnerability/GHSA-89px-ww3j-g2mm)
- <https://github.com/labd/wagtail-2fa/security/advisories/GHSA-89px-ww3j-g2mm>
- <https://nvd.nist.gov/vuln/detail/CVE-2019-16766>
- <https://github.com/labd/wagtail-2fa/commit/13b12995d35b566df08a17257a23863ab6efb0ca>
- <https://github.com/labd/wagtail-2fa/commit/a6711b29711729005770ff481b22675b35ff5c81>
- <https://github.com/labd/wagtail-2fa>
- <https://github.com/pypa/advisory-database/tree/main/vulns/wagtail-2fa/PYSEC-2019-135.yaml>

Facts on this page come from the GitHub Advisory Database (CC-BY 4.0), OSV and the other sources listed, as published. We don’t reproduce full advisory descriptions, which can contain exploit code.

## Check whether this affects you

A Match means an installed version is in the affected range above. Most don’t affect the app; agentprime hasn’t analysed this one yet.

- With the agentprime MCP server (<https://api.agentprime.io/mcp>), ask your agent to check the project: `check_lockfile` sends a lockfile, `check_packages` a list of installed packages, and both return the Matches and the upgrades that clear them. `get_advisory` returns this record. Setup: <https://agentprime.io/mcp.md>
- In a browser: <https://agentprime.io/check/> reads your lockfile in the browser, never uploading it.
- Whether it touches your code, with file and line: the Claude Code plugin, <https://agentprime.io/plugin.md>
- As JSON: <https://api.agentprime.io/v1/advisories/GHSA-89px-ww3j-g2mm>, or `POST https://api.agentprime.io/v1/match` with your packages (<https://agentprime.io/api.md>)

---

The web page: <https://agentprime.io/advisories/GHSA-89px-ww3j-g2mm/>. Everything for agents: <https://agentprime.io/llms.txt>.
