Security fix guide
Missing Content Security Policy
No Content-Security-Policy header found. CSP helps prevent cross-site scripting (XSS) and data injection attacks.
Issue ID: SEC-CSP-001
Severity: medium
Impact: Med
Effort: M
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
No Content-Security-Policy header found. CSP helps prevent cross-site scripting (XSS) and data injection attacks.
Why it matters
No Content-Security-Policy header found. CSP helps prevent cross-site scripting (XSS) and data injection attacks. 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-CSP-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 a Content-Security-Policy header to server responses
- 2Start with a report-only policy: Content-Security-Policy-Report-Only: default-src 'self'
- 3Gradually tighten the policy based on reported violations
- 4Use nonce or hash values for inline scripts
How to re-check it
- Check response headers for Content-Security-Policy with browser DevTools
Related tools
This issue is best verified with the full FreeSiteAudit crawl rather than a single-point mini tool.