Security fix guide
Weak Content Security Policy
The Content-Security-Policy header is present but uses unsafe directives (unsafe-inline, unsafe-eval, or wildcard sources) that significantly reduce its effectiveness.
Issue ID: SEC-CSP-QUALITY-001
Severity: moderate
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
The Content-Security-Policy header is present but uses unsafe directives (unsafe-inline, unsafe-eval, or wildcard sources) that significantly reduce its effectiveness.
Why it matters
The Content-Security-Policy header is present but uses unsafe directives (unsafe-inline, unsafe-eval, or wildcard sources) that significantly reduce its effectiveness. 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-QUALITY-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
- 1Remove unsafe-inline and use nonce-based or hash-based script allowlisting
- 2Remove unsafe-eval and refactor code that uses eval()
- 3Replace wildcard (*) sources with specific domain allowlists
How to re-check it
- Check CSP header and confirm no unsafe-inline, unsafe-eval, or wildcard sources
Related tools
This issue is best verified with the full FreeSiteAudit crawl rather than a single-point mini tool.