{"action":"Upgrade wagtail-2fa to 1.3.0 or later.","affected":[{"fixed":"1.3.0","introduced":"0"}],"component":"wagtail-2fa","cve_ids":["CVE-2019-16766"],"ecosystem":"PyPI","epss":0.01462,"exploited":false,"fixed_versions":["1.3.0"],"ghsa_id":"GHSA-89px-ww3j-g2mm","id":"tcs_01M5KG8GZXCJDRJDZEMQXF9HK1","modified_at":"2023-11-08T04:01:20.782659Z","published_at":"2019-11-29T17:15:00Z","references":["https://osv.dev/vulnerability/PYSEC-2019-135","https://github.com/LabD/wagtail-2fa/security/advisories/GHSA-89px-ww3j-g2mm","https://github.com/labd/wagtail-2fa/commit/13b12995d35b566df08a17257a23863ab6efb0ca","https://github.com/labd/wagtail-2fa/commit/a6711b29711729005770ff481b22675b35ff5c81"],"severity":{"label":"unknown"},"sources":[{"source":"osv","source_id":"PYSEC-2019-135","url":"https://osv.dev/vulnerability/PYSEC-2019-135"}],"summary":"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 dev"}