CVE-2024-5657 is a low-severity (CVSS 3.7) CWE-499 vulnerability in born05/craft-twofactorauthentication. 2 public exploit or proof-of-concept references are indexed, so weaponization risk is real. A fix is available for born05/craft-twofactorauthentication — see the affected versions and patch details below.
CraftCMS Plugin - Two-Factor Authentication - Password Hash Disclosure
Exploitation Status
No confirmed exploitation observed yet
- 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 CVE-2024-5657.
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
born05/craft-twofactorauthenticationReal-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 CraftCMS plugin Two-Factor Authentication in versions 3.3.1, 3.3.2 and 3.3.3 discloses the password hash of the currently authenticated user after submitting a valid TOTP.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 🐘Packagist | born05/craft-twofactorauthentication | ≥ 3.3.1&&< 3.3.4 | 3.3.4composer require born05/craft-twofactorauthentication:^3.3.4 |
Affected Products
two-factor authenticationborn05Research use only. For defensive security, authorized penetration testing, and academic research only. Never execute exploit code against systems without explicit written authorization.
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for born05/craft-twofactorauthentication, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update born05/craft-twofactorauthentication to 3.3.4 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2024-5657 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 CVE-2024-5657 in your dependencies?
Find it across Packagist, including transitive dependencies.