PYSEC-2019-65 - When using wagtail-2fa before 1.3.0, if someone gains access to someone's Wagtail login credentials…

Severity: info · Published 2019-11-29

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.

Technologies: wagtail-2fa (PyPI). Vendors: PyPI.

Quick answers

Is This vulnerability exploited in the wild?
No. Junglewise Threat Intelligence has no report of This vulnerability being exploited in the wild.
How severe is This vulnerability?
Informational severity, published 29 November 2019.
Which products and versions are affected?
wagtail-2fa (PyPI) GIT:introduced=0,fixed=13b12995d35b566df08a17257a23863ab6efb0ca,fixed=a6711b29711729005770ff481b22675b35ff5c81|ECOSYSTEM:introduced=0,fixed=1.3.0.
Is there a fix for This vulnerability?
Yes. wagtail-2fa (PyPI): upgrade to 1.3.0 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
Am I affected?
Check whether you run wagtail-2fa (PyPI) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

How to fix

  • wagtail-2fa (PyPI): upgrade to 1.3.0 or later
    pip install "wagtail-2fa>=1.3.0"

Affected products

  • wagtail-2fa (PyPI) GIT:introduced=0,fixed=13b12995d35b566df08a17257a23863ab6efb0ca,fixed=a6711b29711729005770ff481b22675b35ff5c81|ECOSYSTEM:introduced=0,fixed=1.3.0

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.