Executive brief
Filament is a Laravel-based admin panel UI framework. When multi-factor authentication is enabled, the login page checks password validity before verifying panel access permissions. An attacker can use differing error messages to determine if a password is correct for accounts denied panel access, and may receive MFA codes if email-based MFA is configured. No authentication bypass occurs, as access control is still enforced after the challenge.
Technical details
This information disclosure vulnerability exists in Filament's login flow when multi-factor authentication (MFA) is enabled. The root cause is an order-of-operations issue: the MFA challenge is presented before the `canAccessPanel()` authorization check. For accounts that fail `canAccessPanel()`, a correct password submission renders the MFA challenge, while an incorrect password returns a generic failure message. This allows an unauthenticated attacker to enumerate valid passwords for denied accounts via observable response discrepancy (CWE-204). When email-based MFA is in use, the attacker may also trigger MFA code delivery. The vulnerability has high attack complexity and requires knowledge of specific accounts with MFA enabled and denial policies. Authentication is not bypassed—the access control check still executes after challenge completion, preventing session creation for denied accounts. Patches are available in versions 4.12.5 and 5.7.5.
Affected products
- filamentphp Filament 4.0.0 to 4.12.4, 5.0.0 to 5.7.4
Timeline
- 2026-08-17: disclosed: Published to GitHub Advisory Database
- 2026-09-01: advisory: Updated and reviewed on GitHub Advisory Database
- 2026: patched: Fixed in versions 4.12.5 and 5.7.5