Laravel Hijacked authentication cookies vulnerability
Published 15 May 2024 · Updated 29 Nov 2024
Is your project on an affected laravel/framework?
Affected package
- Affected
- >=4.0.0 <4.1.26
- Fixed in
- 4.1.26
composer require laravel/framework:^4.1.26Details
Laravel 4.1.26 introduces security improvements for "remember me" cookies. Before this update, if a remember cookie was hijacked by another malicious user, the cookie would remain valid for a long period of time, even after the true owner of the account reset their password, logged out, etc.
This change requires the addition of a new remember_token column to your users (or equivalent) database table. After this change, a fresh token will be assigned to the user each time they login to your application. The token will also be refreshed when the user logs out of the application. The implications of this change are: if a "remember me" cookie is hijacked, simply logging out of the application will invalidate the cookie.
Is GHSA-p62r-7637-3wwc in any of your client repos?
Checking one package by hand is fine. Checking it across forty client projects is not. NPMscan reads the lockfiles in every GitHub repo you pick, finds each project with an affected laravel/framework, and gives you the command that fixes it.
More advisories for laravel/framework
- CriticalCVE-2026-114509Laravel TokenGuard authentication bypass through non-string API credentials · 23 Oct 2026
- MediumCVE-2026-114508Laravel relationship inclusion can trigger unauthorized data destruction · 23 Oct 2026
- LowCVE-2026-102279Laravel: XSS in Debug Page Information · 29 Sept 2026
- MediumGHSA-crmm-hgp2-wgrpLaravel Framework: Temporary Signed URL Path Confusion · 17 Jun 2026
- HighCVE-2026-48019Laravel Framework: CRLF injection in default email rule · 17 Jun 2026
- MediumCVE-2024-13918Laravel framework susceptible to reflected cross-site scripting · 10 Mar 2025
References
Advisory data from OSV.dev (opens OSV.dev in a new tab), refreshed daily.