NIST deprecates RSA-2048 from 2030. Find every one of them before attackers do.
🐍
🐍 PyPI
Not in CISA KEV
HIGH severity

Improper Authentication in django-mfa3GHSA-3r7g-wrpr-j5g4

HIGHFix: xi/django-mfa3@32f656e

GHSA-3r7g-wrpr-j5g4 is a high-severity (CVSS 7.3) Improper Authentication vulnerability in django-mfa3. A fix is available for django-mfa3 — see the affected versions and patch details below.

Also known asCVE-2022-24857PYSEC-2022-192
Published
Updated
Affected
1 pkg
Patched
1 / 1
Exploits
None indexed
Exploitation data as of Nov 7, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

EPSS Exploitation Probability

via FIRST.org ↗
1.2%probability of exploitation in next 30 days
Lower Risk0.00%
Lower risk than most CVEs68th percentile — riskier than 68% of all scored CVEsHighest risk
0.01%0.56%1.11%1.67%0.5%1.2%May 26Sep 26Nov 26

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
🐍django-mfa3

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

django-mfa3 is a library that implements multi factor authentication for the django web framework. It achieves this by modifying the regular login view. Django however has a second login view for its admin area. This second login view was not modified, so the multi factor authentication can be bypassed.

You are affected if you have activated both django-mfa3 (< 0.5.0) and django.contrib.admin and have not taken any other measures to prevent users from accessing the admin login view.

Patches

The issue has been fixed in django-mfa3 0.5.0.

Workarounds

It is possible to work around the issue by overwriting the admin login route, e.g. by adding the following URL definition before the admin routes:

url('admin/login/', lambda request: redirect(settings.LOGIN_URL)

References

Affected Packages

1 total 1 fixed
EcosystemPackageVulnerable rangeFix
🐍PyPIdjango-mfa3all versions0.5.0pip install --upgrade 'django-mfa3==0.5.0'

Affected Products

1 product · 1 configurations
Application
django-mfa3django-mfa3_project
< 0.5.0
range

Detection & mitigation playbook

Open-source dependency

  1. Detect

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

  2. Fix

    Update django-mfa3 to 0.5.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-3r7g-wrpr-j5g4 is resolved across your whole dependency graph.

  3. 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 django-mfa3 is a library that implements multi factor authentication for the django web framework. It achieves this by modifying the regular login view. Django however has a second login view for its admin area. This second login view was not modified, so the multi factor authentication can be bypassed. You are affected if you have activated both django-mfa3 (< 0.5.0) and django.contrib.admin and have not taken any other measures to prevent users from accessing the admin login view. ### Patches The issue has been fixed in django-mfa3 0.5.0. ### Workarounds It is possible to wo
O3 Security · Impact-Aware SCA

Is GHSA-3r7g-wrpr-j5g4 in your dependencies?

Find it across PyPI, including transitive dependencies.

Scan my dependencies How O3 SCA works
Improper Authentication in django-mfa3 (High 7.3)