How to fix: Laravel session cookie missing security attributes
The Laravel session cookie is present but may lack Secure, HttpOnly, or SameSite attributes.
Why it matters
A Laravel session cookie without HttpOnly can be stolen via XSS. Without Secure, it is sent over HTTP. Without SameSite, it enables CSRF attacks; all three together make session hijacking significantly easier.
Laravel session cookies must be configured with all three security attributes: Secure (HTTPS only), HttpOnly (no JS access), and SameSite (CSRF protection).
How to fix it
- 1Set SESSION_SECURE_COOKIE=true in .env
- 2In config/session.php: "secure" => true, "http_only" => true, "same_site" => "strict"
Code examples
config/session.php
return [
"driver" => "file",
"secure" => true, // HTTPS only
"http_only" => true, // no JS access
"same_site" => "strict", // CSRF protection
"encrypt" => true,
"lifetime" => 120,
];References
Detected automatically by VulnRadar. The check id is laravel-session-cookie-exposes, stable across every scan so you can filter or diff on it.
More info disclosure checks
- MediumRails Session Cookie Missing HttpOnly Flag
- InfoServer header truncated
- InfoPHP session cookie naming exposes runtime
- Infoconfig.js / settings.js referenced (verify contents)
- Infoenv.js / environment.js referenced (verify contents)
- InfoSitemap.xml publicly accessible
- InfoOpenAPI schema version exposed in URL
- LowCORS exposes internal CDN hostname
Questions
- How severe is Laravel session cookie missing security attributes?
- VulnRadar rates this medium severity in the info disclosure category. The severity is fixed per check, not scored per site, so the same finding is the same severity on every scan.
- Does VulnRadar check for this automatically?
- Yes. It runs as part of every scan under the check id laravel-session-cookie-exposes, which stays the same between runs so you can filter, diff, or gate CI on it.
- Which standards does Laravel session cookie missing security attributes map to?
- It maps to CWE-614. In the OWASP Top 10 it falls under A05:2021.
Missing a check?
The detection set is open. If you know a misconfiguration this does not catch, propose it: the issue template asks for the threat model, how to detect it, the false-positive risk, and a test fixture, which is the same thing a maintainer would have to work out anyway.