How severe is GHSA-9gjv-6qq6-v7qm?

GHSA-9gjv-6qq6-v7qm has a CVSS score of 7.6/10, rated HIGH. Immediate patching is strongly recommended.

Which packages are affected by GHSA-9gjv-6qq6-v7qm?

GHSA-9gjv-6qq6-v7qm affects the following packages: wagtail-2fa (PyPI). Ecosystems affected: PyPI.

How do I fix GHSA-9gjv-6qq6-v7qm?

Update wagtail-2fa to 1.4.1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-9gjv-6qq6-v7qm is resolved across your whole dependency graph.

How do I detect GHSA-9gjv-6qq6-v7qm in my PyPI dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for wagtail-2fa, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate GHSA-9gjv-6qq6-v7qm if there is no patch (or I can't update yet)?

Put an independent control in front of the weakness: restrict the affected endpoint or interface to trusted networks, require an additional authentication factor or proxy-level check, and invalidate existing sessions and credentials in case the flaw has already been used.

Is GHSA-9gjv-6qq6-v7qm actively exploited in the wild?

No public exploit code has been indexed for GHSA-9gjv-6qq6-v7qm yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

What is the EPSS score for GHSA-9gjv-6qq6-v7qm?

GHSA-9gjv-6qq6-v7qm has an EPSS (Exploit Prediction Scoring System) score of 1.0%, placing it in the 63th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

What type of vulnerability is GHSA-9gjv-6qq6-v7qm?

GHSA-9gjv-6qq6-v7qm is classified as CWE-285 (CWE-285), CWE-863 (CWE-863). These weakness types describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was GHSA-9gjv-6qq6-v7qm published, and has it been updated?

GHSA-9gjv-6qq6-v7qm was published on March 13, 2020 and was last updated on September 10, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

🐍

🐍 PyPI

Not in CISA KEV

HIGH severity

2FA bypass through deleting devices in wagtail-2faGHSA-9gjv-6qq6-v7qm

HIGHFix: labd/wagtail-2fa@ac23550

GHSA-9gjv-6qq6-v7qm is a high-severity (CVSS 7.6) CWE-285 vulnerability in wagtail-2fa. A fix is available for wagtail-2fa — see the affected versions and patch details below.

Also known asCVE-2020-5240PYSEC-2020-219

Published

Mar 13, 2020

Updated

Sep 10, 2026

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

Exploitation data as of Nov 6, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

EPSS Exploitation Probability

via FIRST.org ↗

1.0%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs63th percentile — riskier than 63% of all scored CVEsHighest risk

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

How urgent is this, really

Where this sits among everything scored

Real-World Exposure

1 pkg affected

🐍wagtail-2fa

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects PyPI packages — download data is not available via public APIs for these ecosystems.

Description

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
Email us at [email protected]

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
🐍PyPI	`wagtail-2fa`	all versions	1.4.1`pip install --upgrade 'wagtail-2fa==1.4.1'`

Affected Products

1 product · 1 configurations

Application

wagtail-2falabdigital

< 1.4.1

range

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for wagtail-2fa, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update wagtail-2fa to 1.4.1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-9gjv-6qq6-v7qm is resolved across your whole dependency graph.
Workarounds
Put an independent control in front of the weakness: restrict the affected endpoint or interface to trusted networks, require an additional authentication factor or proxy-level check, and invalidate existing sessions and credentials in case the flaw has already been used.

Frequently Asked Questions

### 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