Missing Content-Security-Policy header
Why it matters
No Content-Security-Policy header is set, so the browser has no allowlist restricting which scripts and resources may load, weakening XSS protection.
What to do
Add the missing security header at the server/CDN level.
How to fix it
- Add the missing header at the web server, CDN, or platform configuration level (exact method depends on hosting).
- Start with a permissive policy (e.g. CSP report-only mode) and tighten iteratively to avoid breaking functionality.
- Re-test with a header-scanning tool after each change.
