# CVE-2022-24857: Multi factor authentication bypass in django-mfa3

> Attackers can bypass multi-factor authentication by accessing the unmodified Django admin login view, requiring users to upgrade the library or configure routes.

- **Severity:** High 7.3 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:U/C:H/I:H/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** Yes
- **Published:** 15 Apr 2022
- **Updated:** 23 Apr 2025
- **Also known as:** GHSA-3r7g-wrpr-j5g4, PYSEC-2022-192

## What is CVE-2022-24857?

CVE-2022-24857 is a high-severity authentication bypass vulnerability in xi django-mfa3, published on 15 Apr 2022. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.

### Official description

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. Users are affected if they 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. The issue has been fixed in django-mfa3 0.5.0. 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)

Weakness: CWE-287 (Improper Authentication)

## Which versions are affected by CVE-2022-24857?

3 open source packages ship an affected version, including django-mfa3. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `django-mfa3` | PyPI | All versions | 0.5.0 |
| `django-mfa3` | PyPI | All versions | 0.5.0 |
| `django-mfa3` | PyPI | All versions | 0.5.0 |

Products: Django-Mfa3 Project Django-Mfa3.

## How do I fix CVE-2022-24857?

Upgrade django-mfa3 to 0.5.0 or later.

## Is CVE-2022-24857 being exploited?

There is no known exploitation of CVE-2022-24857 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2022-24857 and fix it if it is affected.

What it is: CVE-2022-24857 is a high-severity authentication bypass vulnerability in xi django-mfa3, published on 15 Apr 2022. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2022-24857 in the wild and no public exploit code.

Affected packages and fixed versions:
- django-mfa3 (PyPI): affected all versions; fixed in 0.5.0
- django-mfa3 (PyPI): affected all versions; fixed in 0.5.0
- django-mfa3 (PyPI): affected all versions; fixed in 0.5.0

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2022-24857/ (Markdown: https://insights.sbomify.com/CVE-2022-24857/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2022-24857
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2022-24857
- OSV: https://osv.dev/vulnerability/CVE-2022-24857

---
From sbomify Insights: https://insights.sbomify.com/CVE-2022-24857/
Summaries are generated and may contain mistakes; the official description above is the record.