CVE-2025-67507
BaseFortify
Publication date: 2025-12-10
Last updated on: 2026-03-04
Assigner: GitHub, Inc.
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| filamentphp | filament | From 4.0.0 (inc) to 4.3.1 (exc) |
Helpful Resources
Exploitability
| CWE ID | Description |
|---|---|
| CWE-287 | When an actor claims to have a given identity, the product does not prove or insufficiently proves that the claim is correct. |
| CWE-288 | The product requires authentication, but the product has an alternate path or channel that does not require authentication. |
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?
This vulnerability exists in Filament versions 4.0.0 through 4.3.0 and involves the handling of recovery codes for app-based multi-factor authentication (MFA). The flaw allows the same recovery code to be reused indefinitely, which should not normally be possible. This issue only affects app-based MFA recovery codes when recovery codes are enabled and does not affect email-based MFA. The vulnerability is fixed in version 4.3.1.
How can this vulnerability impact me? :
The vulnerability can allow an attacker to reuse the same recovery code multiple times to bypass app-based multi-factor authentication protections. This could lead to unauthorized access to user accounts, compromising confidentiality, integrity, and availability of the affected system or data.
What immediate steps should I take to mitigate this vulnerability?
Upgrade Filament to version 4.3.1 or later, as this version contains the fix for the recovery code reuse vulnerability. Additionally, if recovery codes are enabled, consider disabling them temporarily until the upgrade is applied to prevent indefinite reuse.
How does this vulnerability affect compliance with common standards and regulations (like GDPR, HIPAA)?:
The vulnerability undermines the security of multi-factor authentication by allowing indefinite reuse of recovery codes, which can lead to unauthorized access. This weakens the protection of user authentication and could result in breaches of confidentiality, integrity, and availability of sensitive data. Consequently, it may negatively impact compliance with standards and regulations such as GDPR and HIPAA that require strong access controls and protection of personal and health information. [2]