How to fix: Logout Page Missing Clear-Site-Data Header
A logout page was detected but it does not send the Clear-Site-Data header to clear cookies, storage, and cache.
Why it matters
Without Clear-Site-Data, session artifacts may persist after logout on shared devices.
The Clear-Site-Data header instructs the browser to clear cookies, storage, and cache. It should be sent on logout to ensure complete session termination.
How to fix it
- 1Add 'Clear-Site-Data: "cookies", "storage", "cache"' to logout response headers.
- 2Ensure the header is only sent on logout, not every page.
Code examples
Logout route
return new Response(null, {
status: 302,
headers: {
'Location': '/login',
'Clear-Site-Data': '"cookies", "storage", "cache"',
},
});References
Detected automatically by VulnRadar. The check id is clear-site-data-missing, stable across every scan so you can filter or diff on it.
More headers checks
Questions
- How severe is Logout Page Missing Clear-Site-Data Header?
- VulnRadar rates this low severity in the headers 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 clear-site-data-missing, which stays the same between runs so you can filter, diff, or gate CI on it.
- Which standards does Logout Page Missing Clear-Site-Data Header map to?
- It maps to CWE-613. In the OWASP Top 10 it falls under A07: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.