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.
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
| Score | Rating | CVSS | Vector | Source |
|---|---|---|---|---|
| 8.7 | High | 3.1 | CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:C/C:H/I:H/A:N | 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
Sources
- GitHub Advisory Database: GHSA-89px-ww3j-g2mm
- OSV: GHSA-89px-ww3j-g2mm
- github.com/labd/wagtail-2fa/security/advisories/GHSA-89px-ww3j-g2mm
- nvd.nist.gov/vuln/detail/CVE-2019-16766
- github.com/labd/wagtail-2fa/commit/13b12995d35b566df08a17257a23863ab6efb0ca
- github.com/labd/wagtail-2fa/commit/a6711b29711729005770ff481b22675b35ff5c81
- github.com/labd/wagtail-2fa
- github.com/pypa/advisory-database/tree/main/vulns/wagtail-2fa/PYSEC-2019-135.yaml