Quick answers
- Is CVE-2025-67507 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2025-67507 being exploited in the wild.
- How severe is CVE-2025-67507?
- High severity, with a CVSS score of 8.1, published 10 December 2025.
- Which products and versions are affected?
- Filament >= 4.0.0, < 4.3.1; filament/filament (Packagist) >= 4.0.0, < 4.3.1, ECOSYSTEM:introduced=4.0.0,fixed=4.3.1.
- Is there a fix for CVE-2025-67507?
- Yes. filament/filament (Packagist): upgrade to 4.3.1 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2025-67507 attacked?
- It is attacked over the network, in a software library.
- Am I affected by CVE-2025-67507?
- Check whether you run Filament, Filamentphp Filament or filament/filament (Packagist) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
How to fix
- filament/filament (Packagist): upgrade to 4.3.1 or later
composer require filament/filament:^4.3.1
Technical details
An authentication bypass vulnerability exists in Filament's app-based multi-factor authentication (MFA) implementation. The root cause is improper handling of recovery codes, which fail to be invalidated after their first use, allowing for indefinite reuse. This issue specifically affects app-based MFA when recovery codes are enabled; email-based MFA is not impacted. An attacker who has already compromised a user's primary password and obtained a recovery code can bypass the TOTP/app-based second factor. The vulnerability is patched in version 4.3.1.
Affected products
- filamentphp filament >= 4.0.0, < 4.3.1
Identifiers
- CVE-2025-67507
- GHSA-pvcv-q3q7-266g
Timeline
- 2025-12-09: disclosed
- 2025-12-09: advisory
- 2025-12-09: patched