FilamentPHP - CraftedSignal Threat Feedhttps://feed.craftedsignal.io/vendors/filamentphp/Trending threats, MITRE ATT&CK coverage, and detection metadata. Fed continuously.Hugoenhello@craftedsignal.iohello@craftedsignal.ioWed, 02 Sep 2026 00:00:24 +0000https://feed.craftedsignal.io/favicon-32x32.pngCraftedSignal Threat Feedhttps://feed.craftedsignal.io/3232https://feed.craftedsignal.io/favicon.svgAuthentication Bypass in Filament Framework MFAhttps://feed.craftedsignal.io/briefs/2026-09-filament-mfa-bypass/Wed, 02 Sep 2026 00:00:24 +0000hello@craftedsignal.iohttps://feed.craftedsignal.io/briefs/2026-09-filament-mfa-bypass/An improper authentication vulnerability in the Filament framework allows attackers to bypass app-based multi-factor authentication when recovery codes are enabled.Filament, a popular framework for building administrative panels, contains a critical authentication flaw identified as CVE-2026-77567. The vulnerability exists in the challenge handling logic for app-based multi-factor authentication (MFA). When recovery codes are enabled for a user, the application fails to properly validate the second-factor token, allowing an attacker to bypass the MFA challenge entirely. This flaw is specific to app-based MFA and does not affect configurations using email-based authentication. The issue impacts Filament version branches 4.x (prior to 4.12.0) and 5.x (prior to 5.7.0). Successful exploitation grants an attacker unauthorized access to protected accounts, bypassing a significant layer of security intended to prevent account takeover.

Impact

The vulnerability poses a severe risk to organizations using Filament for administrative interfaces, as it allows unauthorized users with valid primary credentials to bypass the second-factor requirement. This essentially negates the security benefits of MFA for affected users, significantly increasing the likelihood of account compromise, data exfiltration, and unauthorized administrative actions within the application.

Recommendation

Prioritize patching affected systems to mitigate the risk of account takeover.

  • Upgrade the filament/filament package to version 4.12.0 or 5.7.0 immediately.
  • Disable app-based MFA or recovery codes as a temporary workaround until patching is complete if the application must remain internet-facing.
  • Audit authentication logs for unusual login patterns or failed attempts followed by successful access to user accounts in the administrative panel.
  • Review administrative user accounts for unauthorized changes or configuration modifications made since the deployment of vulnerable versions.
]]>highadvisory