Authentication Bypass in extension "E-Mail MFA Provider" (mfa_email)GHSA-29r8-gvx4-r9w3
HIGHFix: MrSilaz/mfa_email@0bb7e85GHSA-29r8-gvx4-r9w3 is a high-severity (CVSS 8.8) CWE-639 vulnerability in ralffreit/mfa-email. A fix is available for ralffreit/mfa-email — see the affected versions and patch details below.
Exploitation Status
No confirmed exploitation observed yet
- A successful exploit gives an attacker total control of the affected component, not partial access.
- CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.
Exploitation and automatability from CISA’s SSVC triage for GHSA-29r8-gvx4-r9w3.
EPSS Exploitation Probability
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
ralffreit/mfa-email🐘ralffreit/mfa-emailReal-time download stats are indexed for npm and PyPI packages. This vulnerability affects Packagist packages — download data is not available via public APIs for these ecosystems.
Description
The extension fails to properly reset the generated MFA code after successful authentication. This leads to a possible MFA bypass for future login attempts by providing an empty string as MFA code to the extensions MFA provider.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 🐘Packagist | ralffreit/mfa-email | all versions | 1.0.7composer require ralffreit/mfa-email:^1.0.7 |
| 🐘Packagist | ralffreit/mfa-email | ≥ 2.0.0&&< 2.0.1 | 2.0.1composer require ralffreit/mfa-email:^2.0.1 |
Affected Products
mfa mailmrsilazDetection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for ralffreit/mfa-email, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update ralffreit/mfa-email to 1.0.7 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-29r8-gvx4-r9w3 is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
Frequently Asked Questions
Is GHSA-29r8-gvx4-r9w3 in your dependencies?
Find it across Packagist, including transitive dependencies.