How severe is CVE-2022-24857?

CVE-2022-24857 has a CVSS score of 7.3/10, rated HIGH. Immediate patching is strongly recommended.

Which packages are affected by CVE-2022-24857?

CVE-2022-24857 affects the following packages: django-mfa3 (PyPI). Ecosystems affected: PyPI.

How do I fix CVE-2022-24857?

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

How do I detect CVE-2022-24857 in my PyPI dependencies?

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.

How do I mitigate CVE-2022-24857 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 CVE-2022-24857 actively exploited in the wild?

No public exploit code has been indexed for CVE-2022-24857 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 CVE-2022-24857?

CVE-2022-24857 has an EPSS (Exploit Prediction Scoring System) score of 1.2%, placing it in the 67th 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 CVE-2022-24857?

CVE-2022-24857 is classified as Improper Authentication (CWE-287). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was CVE-2022-24857 published, and has it been updated?

CVE-2022-24857 was published on April 15, 2022 and was last updated on October 28, 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

CVE-2022-24857 — django-mfa3

HIGHFix: xi/django-mfa3@32f656e

CVE-2022-24857 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.

Multi factor authentication bypass in django-mfa3

Also known asGHSA-3r7g-wrpr-j5g4PYSEC-2022-192

Published

Apr 15, 2022

Updated

Oct 28, 2026

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

Exploitation data as of Nov 2, 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 CVEs67th percentile — riskier than 67% 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

🐍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

django-mfa3 changelog

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
🐍PyPI	`django-mfa3`	all versions	0.5.0`pip 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

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.
Fix
Update django-mfa3 to 0.5.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2022-24857 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 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