csp-bypass-advanced

Identify Content Security Policy bypass opportunities for web application testing.

11|4|Updated Jun 7, 2026
One-click install
npx skills add https://github.com/sayseven7/frameseven --skill csp-bypass-advanced-sayseven7
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: csp-bypass-advanced
Source: https://github.com/sayseven7/frameseven/tree/main/internal/mcp/skills/csp-bypass-advanced
Command: npx skills add https://github.com/sayseven7/frameseven --skill csp-bypass-advanced-sayseven7

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps security testers identify and reason about Content Security Policy weaknesses that still allow XSS, data exfiltration, or script execution even when a policy is present.

Core Features & Use Cases

  • Policy analysis: Evaluates CSP headers and meta policies, including directive fallbacks and missing protections such as base-uri, form-action, and frame-ancestors.
  • Bypass strategy mapping: Surfaces practical attack paths like trusted CDN abuse, nonce or hash weaknesses, strict-dynamic trust propagation, and framework-specific gadget abuse.
  • Exfiltration planning: Recommends alternate channels when normal script execution is blocked, including DNS-based leakage, form submission, CSS-driven exfiltration, and report-uri side effects.
  • Use case: Use this Skill when auditing a target application and you need to quickly determine whether its CSP can be bypassed through policy gaps, browser behavior, or trusted script paths.

Quick Start

Ask the AI to review the target page’s CSP and enumerate the most likely bypass vectors, missing directives, and exfiltration channels.

Frequently Asked Questions about csp-bypass-advanced

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I test if a web application's CSP can be bypassed for XSS?

Analyze CSP headers and meta tags to identify missing directives like base-uri, form-action, and frame-ancestors, then map practical attack paths such as trusted CDN abuse, strict-dynamic trust propagation, or nonce weaknesses to execute XSS.

What are common Content Security Policy bypass techniques?

Common CSP bypass techniques involve abusing trusted CDNs, exploiting nonce or hash weaknesses, leveraging strict-dynamic trust propagation, and using framework-specific gadgets to achieve script execution or data exfiltration.

How can I exfiltrate data when CSP blocks normal script execution?

When normal script execution is blocked by CSP, you can exfiltrate data through alternative channels including DNS-based leakage, direct form submission, CSS-driven exfiltration, or triggering side effects via the report-uri directive.

Does strict-dynamic trust propagation introduce CSP bypass risks?

Yes, strict-dynamic trust propagation allows scripts added by trusted scripts to execute, creating bypass risks if attackers can abuse framework-specific gadgets or inject scripts via trusted CDN paths to bypass the whitelist.

What missing CSP directives allow data exfiltration or XSS?

Missing CSP directives that allow exfiltration or XSS include base-uri, form-action, and frame-ancestors, which leave gaps for attackers to hijack form submissions, inject malicious base URLs, or frame the application.