Skip to main content
HighHeadersOWASP A05:2021CWE-693

How to fix: Missing Content Security Policy (CSP)

No Content-Security-Policy header was found. CSP helps prevent cross-site scripting (XSS) and data injection attacks.

Why it matters

Without CSP, the site is more vulnerable to XSS attacks because browsers have no policy to restrict which scripts and resources can execute.

Content Security Policy is a defense-in-depth mechanism that restricts which resources the browser is allowed to load. By defining a strict policy, you prevent attackers from injecting malicious scripts.

How to fix it

  1. 1Define a Content-Security-Policy header with restrictive defaults.
  2. 2Start with a report-only policy to identify issues.
  3. 3Use 'self' as the default-src and explicitly allow trusted origins.
  4. 4Avoid 'unsafe-inline' and 'unsafe-eval' where possible; use nonces or hashes instead.

Code examples

Next.js

JavaScript
const nextConfig = {
  async headers() {
    return [{
      source: '/(.*)',
      headers: [{ key: 'Content-Security-Policy', value: "default-src 'self'; script-src 'self'; style-src 'self' 'unsafe-inline'; img-src 'self' data:; font-src 'self';" }],
    }];
  },
};

Nginx

nginx
add_header Content-Security-Policy "default-src 'self'; script-src 'self'; style-src 'self' 'unsafe-inline'; img-src 'self' data:;" always;

Apache

APACHE
Header always set Content-Security-Policy "default-src 'self'; script-src 'self'; style-src 'self' 'unsafe-inline'; img-src 'self' data:;"

Caddy

PLAINTEXT
header Content-Security-Policy "default-src 'self'; script-src 'self'; style-src 'self' 'unsafe-inline'; img-src 'self' data:;"

Express (Node.js)

JavaScript
app.use((req, res, next) => {
  res.setHeader('Content-Security-Policy',
    "default-src 'self'; script-src 'self'; style-src 'self' 'unsafe-inline'; img-src 'self' data:;");
  next();
});

Deno (Hono)

TypeScript
app.use('*', async (c, next) => {
  await next();
  c.header('Content-Security-Policy',
    "default-src 'self'; script-src 'self'; style-src 'self' 'unsafe-inline'; img-src 'self' data:;");
});

Bun (Elysia)

TypeScript
app.onAfterHandle(({ set }) => {
  set.headers['Content-Security-Policy'] =
    "default-src 'self'; script-src 'self'; style-src 'self' 'unsafe-inline'; img-src 'self' data:;";
});

HTML Meta Tag

HTML
<meta http-equiv="Content-Security-Policy" content="default-src 'self'; script-src 'self';">

References

Detected automatically by VulnRadar. The check id is csp-missing, stable across every scan so you can filter or diff on it.

See every headers check

Questions

How severe is Missing Content Security Policy (CSP)?
VulnRadar rates this high 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 csp-missing, which stays the same between runs so you can filter, diff, or gate CI on it.
Which standards does Missing Content Security Policy (CSP) map to?
It maps to CWE-693. In the OWASP Top 10 it falls under A05: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.

Propose a checkHow a check is built

Scan your own site for missing content security policy (csp)

VulnRadar runs this check and hundreds more against a URL in seconds. No agent to install, just paste a URL.

Or scan this site as a demoRead the docs

Missing Content Security Policy (CSP) fix | VulnRadar