CVE-2020-5240
mediumpriority · track · 34OT risk · elevatedEPSS 0.010 · 63 %ileEUUSEPSS · scored 2026-10-27
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.
cvss
Technical severity, 0–10. One row per scoring source.
base score 0–10 · higher = more severe · hover a vector to decode⚠ sources disagree · medium–high · 5.5–8.5
weaknesses
The CWE weakness classes this flaw belongs to.
affected products (3)
Products and version ranges known to be affected.
advisories (2)
Vendor and ecosystem advisories describing this.
- GHSA-9gjv-6qq6-v7qm2FA bypass through deleting devices in wagtail-2fa2020-03-13ghsa · osvUS
### Impact 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 user's device they can disable the target user's 2FA devices and potentially compromise the account if they figure out their password. ### Patches The problem has been patched in version 1.4.1. ### Workarounds There is no workaround for this issue. ### For more information If you have any questions or comments about this advisory: * Open an issue in [github.com/labd/wagtail-2fa](https://github.com/labd/wagtail-2fa) * Email us at [security@labdigital.nl](mailto:security@labdigital.nl)
- PYSEC-2020-2192020-03-13vendor · osvUS
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.
also known as (6)
Other names and identifiers for this entity.
sources
Which sources assert this record, and when.
references (7)
External citations — patches, advisories, analysis.
- https://github.com/labd/wagtail-2fa/commit/ac23550d33b7436e90e3beea904647907eba5b74cnnvd
- https://github.com/labd/wagtail-2fa/security/advisories/GHSA-9gjv-6qq6-v7qmcnnvd
- https://nvd.nist.gov/vuln/detail/CVE-2020-5240cnnvd
- https://github.com/labd/wagtail-2fa/commit/ac23550d33b7436e90e3beea904647907eba5b74enisa_euvd
- https://github.com/labd/wagtail-2fa/security/advisories/GHSA-9gjv-6qq6-v7qmenisa_euvd
- https://github.com/labd/wagtail-2fa/commit/ac23550d33b7436e90e3beea904647907eba5b74PatchThird Party Advisorynvd
- https://github.com/labd/wagtail-2fa/security/advisories/GHSA-9gjv-6qq6-v7qmThird Party Advisorynvd
Attackers weaponise vulnerabilities like this against internet-exposed services. See what is exposed on your perimeter with a free passive scan.
Free scan