Read the docs
TI-2024-38662 Aliases GHSA-q4xf-7fw5-4x8v

Laravel Hijacked authentication cookies vulnerability

Priority LOW 38CWE-384Published · Updated

Key facts

Attack vector
—
Privileges required
—
User interaction
—
Attack complexity
—
Impact type
Spoofing
Confidentiality · integrity · availability
—
Fix status
Fixed

No CVSS vector from any source. Fix status from GitHub. Impact type from CWE-384.

Summary

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.

Why it matters now

Fix Fixed illuminate/auth (Packagist): 4.1.26

SSVC decision points

Not available: CISA has not published SSVC decision points for this record.

Affected products

VendorProductAffected versionsFixed inStatusSource
—illuminate/auth (Packagist)4.0.0 to before 4.1.264.1.26Patch availableGHSA-q4xf-7fw5-4x8v
  • illuminate/auth (Packagist) Vendor— Affected 4.0.0 to before 4.1.26 Fixed in 4.1.26 Patch available GHSA-q4xf-7fw5-4x8v

Remediation

  • Fix · GHSA-q4xf-7fw5-4x8v illuminate/auth (Packagist) Fixed in 4.1.26 Advisory →

Timeline

  1. 2026-10-03 Threatist record created from GHSA-q4xf-7fw5-4x8v

References

Sources

This product uses the NVD API but is not endorsed or certified by the NVD. Sources and licences