GHSA-p62r-7637-3wwc
Laravel Hijacked authentication cookies vulnerability
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.
What each source reports
GitHub AdvisoriesNo score
Laravel Hijacked authentication cookies vulnerability
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.
- Record
GHSA-p62r-7637-3wwc- Weakness
- CWE-384
- Updated
- 2026-11-02
OSVNo score
Laravel Hijacked authentication cookies vulnerability
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.
- Record
GHSA-p62r-7637-3wwc- Weakness
- CWE-384
- Updated
- 2026-11-02
Affected packages
| Package | Affected | Fixed |
|---|---|---|
laravel/frameworkPackagist | 4.0.0 up to 4.1.26 | 4.1.26 |
laravel/frameworkPackagist | 4.0.0 up to 4.1.26, plus listed versions v4.0.0v4.0.1v4.0.10v4.0.11v4.0.2 Show 33 moreShow lessv4.0.3v4.0.4v4.0.5v4.0.6v4.0.7v4.0.8v4.0.9v4.1.0v4.1.1v4.1.10v4.1.11v4.1.12v4.1.13v4.1.14v4.1.15v4.1.16v4.1.17v4.1.18v4.1.19v4.1.2v4.1.20v4.1.21v4.1.22v4.1.23v4.1.24v4.1.25v4.1.3v4.1.4v4.1.5v4.1.6v4.1.7v4.1.8v4.1.9 | 4.1.26 |
History
| Recorded | Changed | Sources |
|---|---|---|
| first indexed | GitHub Advisories, OSV |
Dates are when Every CVE recorded each change. Upstream dates may differ.
In short
GHSA-p62r-7637-3wwc is a vulnerability with no CVSS score yet in laravel/framework, published May 15, 2024. No source lists public exploit code. Fixed in laravel/framework 4.1.26.