Filament: Password validity disclosure for accounts denied panel access on login page
Published 1 Sept 2026 · Updated 1 Sept 2026
Affected packages
- Affected
- >=4.0.0 <4.12.5
- Fixed in
- 4.12.5
composer require filament/filament:^4.12.5- Affected
- >=5.0.0 <5.7.5
- Fixed in
- 5.7.5
composer require filament/filament:^5.7.5Details
When multi-factor authentication is enabled, the login page presents the multi-factor challenge before evaluating canAccessPanel(). For an account that canAccessPanel() denies, submitting the correct password renders the challenge while an incorrect password returns the generic failure message, allowing an unauthenticated attacker to confirm that a password is valid for that account. When email-based multi-factor authentication is used, a login code is also sent to the account holder.
This issue only applies to accounts that both have multi-factor authentication enabled and are denied by canAccessPanel(). Authentication is not bypassed as the check still runs after the challenge, and no session is created.
Is GHSA-xwpv-pqxp-5v36 in any of your client repos?
Checking one package by hand is fine. Checking it across forty client projects is not. NPMscan reads the lockfiles in every GitHub repo you pick, finds each project with an affected filament/filament, and gives you the command that fixes it.
References
- Linkgithub.com/filamentphp/filament/security/advisories/GHSA-xwpv-pqxp-5v36
- Linkgithub.com/filamentphp/filament/pull/20308
- Linkgithub.com/filamentphp/filament/commit/ad5aacbc6d089b3dd7243ec1c1f8ab19dff7c3a1
- Packagegithub.com/filamentphp/filament
- Linkgithub.com/filamentphp/filament/releases/tag/v4.12.5
- Linkgithub.com/filamentphp/filament/releases/tag/v5.7.5
Advisory data from OSV.dev (opens OSV.dev in a new tab), refreshed daily.