Security fix guide
Cookies Missing SameSite Attribute
Cookies are set without the SameSite attribute. While modern browsers default to Lax, explicitly setting it provides better CSRF protection.
Issue ID: SEC-COOKIE-SAMESITE-001
Severity: minor
Impact: Low
Effort: S
Use this article when
- You need deeper remediation guidance than the issue card can show.
- You want CMS-specific steps before handing the fix to a developer.
- You want a repeatable re-check path after shipping the change.
What this issue is
Cookies are set without the SameSite attribute. While modern browsers default to Lax, explicitly setting it provides better CSRF protection.
Why it matters
Cookies are set without the SameSite attribute. While modern browsers default to Lax, explicitly setting it provides better CSRF protection. This affects browser trust signals and whether visitors feel safe submitting contact details.
How we detect it
- FreeSiteAudit flags this issue when the rule for SEC-COOKIE-SAMESITE-001 fails and the page evidence points to Http headers.
- You can usually confirm this by checking the page source or the relevant page settings inside your CMS.
Evidence examples
Check the affected page source, rendered output, or relevant CMS setting to confirm the missing or incorrect element.
How to fix it
- 1Add SameSite=Lax or SameSite=Strict to cookies
- 2Use SameSite=None; Secure only for legitimate cross-site cookies
How to re-check it
- Inspect cookies and confirm all have an explicit SameSite attribute
Related tools
This issue is best verified with the full FreeSiteAudit crawl rather than a single-point mini tool.