Laravel authentication bypass in TokenGuard credential lookup
laravel framework
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| laravel/framework Packagist |
|
|
laravel framework
| Product | Affected | Fixed in |
|---|---|---|
| laravel/framework Packagist |
|
|
Laravel is a web application framework. Prior to 12.68.0 and 13.29.0, TokenGuard configured as a standard token-based API guard does not reject a crafted non-string credential. Under affected MySQL or MariaDB configurations, the authentication lookup can match an unintended existing user, allowing an unauthenticated attacker to bypass authentication and take over an account on routes protected by TokenGuard. This issue is fixed in versions 12.68.0 and 13.29.0.
From the CVE record · GitHub_M
TokenGuard, when configured as a standard token-based API guard, does not reject a crafted non-string credential. Under affected MySQL or MariaDB configurations, an unauthenticated attacker can use it to match another user and take over that account through a TokenGuard-protected route.
Teams running laravel/framework versions >=13.0.0 <13.27.0, >=12.0.0 <12.68.0, >=11.0.0 <11.56.1, or <10.50.4 should check their installations.