GHSA-xwpv-pqxp-5v36: Low severity composer/filament/filament vulnerability

Published Sep 1, 2026
·
Updated

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.

Affected Software

2 affected componentsFixes available
composer/filament/filament>=5.0.0<5.7.5
5.7.5
composer/filament/filament>=4.0.0<4.12.5
4.12.5

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade composer/filament/filament to a version that resolves this vulnerability.

    Fixed in 5.7.5
  2. Upgrade

    Upgrade composer/filament/filament to a version that resolves this vulnerability.

    Fixed in 4.12.5

Event History

Sep 1, 2026
Advisory Published
via GitHub·09:29 PM
Data Sourced
via GitHub·09:29 PM
DescriptionSeverityWeaknessAffected Software

Frequently Asked Questions

1

Which accounts are exposed to this issue?

Only accounts that have multi-factor authentication enabled and for which canAccessPanel() denies panel access are affected. Accounts that do not meet both conditions are not affected by the described password-validation oracle.

2

What does an attacker need to exploit it?

An unauthenticated attacker needs to submit password guesses for an affected account. A correct password causes the multi-factor challenge to appear, while an incorrect password produces a generic failure message.

3

Does this allow an attacker to log in or create a session?

No. Authentication is not bypassed: the access check still runs after the multi-factor challenge, and no session is created.

4

What additional effect occurs with email-based multi-factor authentication?

For affected accounts using email-based multi-factor authentication, a login code is sent to the account holder when the correct password is submitted. This may alert the account holder to password-validation attempts.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203