Skip to main content
No exploitation reportedFix available

CVE-2022-42731

No exploitation reported by the sources we read.

  • Published2022-10-11
  • Fixed in2.6.1 · 2.5.1
  • WeaknessCWE-294

Am I affected?

With a domain, we read the version its public headers and pages expose. A distribution build can carry the fix under an older number.

Description

mfa/FIDO2.py in django-mfa2 before 2.5.1 and 2.6.x before 2.6.1 allows a replay attack that could be used to register another device for a user. The device registration challenge is not invalidated after usage.

Timeline

dates in UTC
  1. 2022-10-1114:15CVE publishedNVD

Versions per branch

NVD · OSV
Django-mfa2 project django-mfa2
BranchAffectedFixed in
2.6≥ 2.6.0, < 2.6.12.6.1
2.5< 2.5.12.5.1

as publishedRanges as NVD and OSV publish them; a distribution’s build can be fixed under an older number.

Fix

  1. Update Django-mfa2 project django-mfa2 to 2.6.1 · 2.5.1

Advisories and patches

Detection

Nuclei template
none so far
ProjectDiscovery
Exploit-DB
no entry
Exploit-DB
Proof of concept
Metasploit modules
none listed
Metasploit Framework

Sources

Identifiers

Technical details

CVSS v3 Vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N
Published
2022-10-11
Last Modified
2026-06-17
NVD status
Modified
GitHub Advisory
GHSA-vw39-2wj9-4q86

Frequently asked questions

What is CVE-2022-42731?

mfa/FIDO2.py in django-mfa2 before 2.5.1 and 2.6.x before 2.6.1 allows a replay attack that could be used to register another device for a user. The device registration challenge is not invalidated after usage.

Is CVE-2022-42731 actively exploited?

Active exploitation of CVE-2022-42731 has not been confirmed. Its EPSS score was 1.5% on 2026-11-09, the estimated probability of exploitation in the next 30 days.

What is the CVSS score for CVE-2022-42731?

CVE-2022-42731 has a CVSS v3 base score of 7.5 (HIGH severity), with vector string CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N.

Running django-mfa2? Hear about its next vulnerability

Surveillance reads the versions in your stack — a domain, a lockfile or a list — checks each CVE against the ranges its sources publish, and alerts you when one you run is exploited or enters CISA KEV. A version it cannot read stays « version not verified ».

Get alerts for this productCISA KEV additions, November 2026Search CVEs

No credit card required · No monthly cap on website lookups · 250 API requests/month

Go further

Related vulnerabilities

Same product first, then the same vendor advisory and the same publication week.

Back to CVE Database

Sources for this record