What Is Missing CSP?
A Content-Security-Policy (CSP) tells the browser which scripts, styles, and resources are allowed to load — your strongest defense-in-depth against cross-site scripting. Most frameworks (Next.js, Vercel, Express) ship no CSP by default, so injected or malicious scripts run freely. A weak CSP (with unsafe-inline or overly broad sources) is barely better than none. We scan and grade your policy.
How Missing CSP Shows Up
No CSP at all
Without a policy, any injected script — from XSS, a compromised dependency, or a malicious ad — executes with full page privileges.
unsafe-inline / unsafe-eval
Policies that allow inline scripts or eval defeat much of CSP's XSS protection.
Overly broad sources
Wildcards or allowing https: everywhere let attacker-controlled domains serve scripts.
Missing related headers
CSP works best alongside X-Frame-Options/frame-ancestors and X-Content-Type-Options to block clickjacking and MIME sniffing.
How the Sable Scan Detects It
Policy grading
We fetch your live headers and grade your CSP (and HSTS, X-Frame-Options, and the rest) A-F.
Weakness detection
We flag unsafe-inline, unsafe-eval, wildcards, and missing directives.
Copy-paste fixes
You get a hardened CSP for Next.js, Vercel, Nginx, or Cloudflare ready to paste.
Check Your App for Missing CSP
Create a free account and let the agents test your app. Every finding is validated with a proof-of-concept and remediation. 150 founder credits, no credit card.
Get 150 Free Credits