CVE-2020-5240: In wagtail-2fa before 1.4.1, any user with access to the CMS can view and delete other users 2FA devices by go

Q: How do I fix CVE-2020-5240?

wagtail-2fa: upgrade to 1.4.1. Exact commands for each OS are on this page.

Q: Is CVE-2020-5240 being exploited?

CVE-2020-5240 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

Q: What does CVE-2020-5240 affect?

CVE-2020-5240 affects wagtail-2fa. Severity is high (CVSS 7.6). In wagtail-2fa before 1.4.1, any user with access to the CMS can view and delete other users 2FA devices by going to the correct path. The user does not require special permissions in order to do so. By deleting the other users device they

This month

HIGH 7.6UPGRADE

CVE-2020-5240 is a high-severity flaw (CVSS 7.6) affecting wagtail-2fa. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

In wagtail-2fa before 1.4.1, any user with access to the CMS can view and delete other users 2FA devices by going to the correct path. The user does not require special permissions in order to do so. By deleting the other users device they can disable the target users 2FA devices and potentially compromise the account if they figure out their password. The problem has been patched in version 1.4.1.

Why this priority

High severity

A fixed release or distro patch exists.

Risk facts

CVSS score	7.6 (High)
Attack vector	Network (remote)
Attack complexity	Low
Privileges needed	Low
User interaction	Required
EPSS exploit chance	1.0% (top 37%)
CISA exploited list	No
Weakness	CWE-285, CWE-863
Published	2020-03-13
Last modified	2026-06-17

Publisher (CNA): GitHub, Inc. · Vendor: labdigital

Last updated 2026-06-17 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score

Am I affected?

Timeline

2020-03-13 22:15 UTCPublished CVE record published
2026-06-17 03:21 UTCUpdated Record last modified

labdigital wagtail-2fa UPGRADE

Affected: < 1.4.1

Fixed in: 1.4.1

Safe to downgrade to: no unaffected older release

1. Check installed version

apt-cache policy wagtail-2fa || rpm -q wagtail-2fa || wagtail-2fa --version

2. UPGRADE to 1.4.1 (Debian / Ubuntu)

sudo apt update && sudo apt install --only-upgrade wagtail-2fa

2. UPGRADE (RHEL / Amazon Linux / Fedora)

sudo dnf upgrade wagtail-2fa

Note

Distros often backport fixes without changing the version number. Confirm with the distro advisory or changelog.

Verify at the official source NVD · CVE Program · Report a problem with this page
Scores and fixes here are computed automatically from those and other public sources. Confirm with the vendor advisory before changing production systems.

Quick answers

How do I fix CVE-2020-5240?

wagtail-2fa: upgrade to 1.4.1. Exact commands for each OS are on this page.

Is CVE-2020-5240 being exploited?

CVE-2020-5240 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

What does CVE-2020-5240 affect?

CVE-2020-5240 affects wagtail-2fa. Severity is high (CVSS 7.6). In wagtail-2fa before 1.4.1, any user with access to the CMS can view and delete other users 2FA devices by going to the correct path. The user does not require special permissions in order to do so. By deleting the other users device they

How urgent is CVE-2020-5240?

Priority 42/100. High severity

Related CVEs

CVE-2019-16766 HIGH 8.7 UPGRADE When using wagtail-2fa before 1.3.0, if someone gains access to someone's Wagtail login credentials, they can

References

← Back to latest CVEs