What the issue means
An insecure cookie is missing one or more protections such as Secure, HttpOnly, or SameSite.
Security fix guide
An insecure cookie is missing one or more protections such as Secure, HttpOnly, or SameSite.
Run Full Website Security ScanAn insecure cookie is missing one or more protections such as Secure, HttpOnly, or SameSite.
Cookie flags reduce the chance of session leakage, script access, and cross-site request abuse.
Inspect Set-Cookie headers in browser devtools or with a website security scan.
Set Secure, HttpOnly, and SameSite on sensitive cookies, especially authentication and session cookies.
Use application code for most cookie flags; proxy_cookie_flags can help when Nginx is acting as a reverse proxy.Use application code for most cookie flags; Header edit Set-Cookie may help for legacy apps.cookies().set("session", value, { secure: true, httpOnly: true, sameSite: "lax" });Prefer application-level cookie flags; use edge rules only when you understand downstream effects.