CFG-001high SeveritySecurity Misconfiguration & Headers
Content Security Policy (CSP) Defined on All HTML Pages
Default Next.js and Vite scaffolds do not include a Content Security Policy header unless explicitly configured in config files.
1-Click Fix Prompt for Cursor & Claude Code
Review my codebase for "Content Security Policy (CSP) Defined on All HTML Pages" (CFG-001). Issue: Default Next.js and Vite scaffolds do not include a Content Security Policy header unless explicitly configured in config files. Remediation required: Add a strict Content-Security-Policy header in middleware or next.config.js restricting script-src and frame-ancestors. Please: 1. Locate any occurrences of this issue across my repository. 2. Refactor the code to follow production standards without breaking existing functionality. 3. Provide a clear command or step to test and verify the fix.
Why AI Assistants Write This Bug
Default Next.js and Vite scaffolds do not include a Content Security Policy header unless explicitly configured in config files.
AI code generation prioritizes immediate syntax execution over production edge cases. When an assistant hits an undefined variable or strict type error, it frequently takes the path of least resistance rather than implementing standard pre-launch security patterns.
Code Comparison
Common AI Code PatternVulnerable
// Vulnerable AI-generated pattern for: Content Security Policy (CSP) Defined on All HTML Pages
// Problematic pattern: Default Next.js and Vite scaffolds do not include a Content Security Policy header unless explicitly configured in config files.Launch-Ready Fix
// Production-ready fix for: Content Security Policy (CSP) Defined on All HTML Pages
// Recommended remediation: Add a strict Content-Security-Policy header in middleware or next.config.js restricting script-src and frame-ancestors.Remediation & Verification Checklist
Remediation: Add a strict Content-Security-Policy header in middleware or next.config.js restricting script-src and frame-ancestors.
- Search your codebase for pattern matching "Content Security Policy (CSP) Defined on All HTML Pages".
- Apply the recommended remediation: Add a strict Content-Security-Policy header in middleware or next.config.js restricting script-src and frame-ancestors.
- Run local build and test commands to ensure no regressions.
- Verify in your browser or with curl that the issue is resolved.
Audit All 108 Checks in One Click
Checking items one by one takes hours. Let us do it in 2 minutes.
With the Founder Pass ($15 one-time), we automatically scan your repository for this issue, plus all other 107 launch checks across secrets, Stripe webhooks, Supabase RLS, and security headers.