Back to catalog
Static reviewDevelopment

Skill dossier

performing-content-security-policy-bypass

Source declaration

Analyze Content-Security-Policy headers and bypass them to achieve cross-site scripting by exploiting unsafe-inline/unsafe-eval, whitelisted JSONP endpoints, base-uri and form-action gaps, and nonce/hash weaknesses, then exfiltrate data even without script-src control. Use during web application security assessments or bug bounty hunting when XSS is found but blocked by CSP, or when auditing CSP header configuration for weaknesses.

The author's original description, preserved in English. It describes intent, not verified performance.

Analyze Content-Security-Policy headers and bypass them to achieve cross-site scripting by exploiting unsafe-inline/unsafe-eval, whitelisted JSONP endpoints, base-uri and form-action gaps, and nonce/hash weaknesses, then exfiltrate data even without script-src control. Use during web application security assessments or bug bounty hunting when XSS is found but blocked by CSP, or when auditing CSP header configuration for weaknesses.

developmentreferencesscripts

Research summary

Machine-generated analysis; pending human review

These observations come from deterministic source parsing, not a human security review or controlled task evaluation.

Analyze Content-Security-Policy headers and bypass them to achieve cross-site scripting by exploiting unsafe-inline/unsafe-eval, whitelisted JSONP endpoints, base-uri and form-action gaps, and nonce/hash weaknesses, then exfiltrate data even without script-src control. Use during web application security assessments or bug bounty hunting when XSS is found but blocked by CSP, or when auditing CSP header configuration for weaknesses. This bilingual summary is generated deterministically from collected source text and file structure; it is pending human editorial review.

Review scope

Deterministic static analysis of collected SKILL.md and supporting text/code. Machine-assisted candidates and findings await human editorial review; no dynamic behavior or effect is assessed.

Observable capabilities

  • Workflow [Source statement; provisional, not tested. Evidence: skills/performing-content-security-policy-bypass/SKILL.md:L52]
  • Step 1 — Analyze the CSP Policy [Source statement; provisional, not tested. Evidence: skills/performing-content-security-policy-bypass/SKILL.md:L54]
  • Step 2 — Exploit unsafe-inline and unsafe-eval [Source statement; provisional, not tested. Evidence: skills/performing-content-security-policy-bypass/SKILL.md:L77]
  • Step 3 — Exploit Whitelisted Domain JSONP Endpoints [Source statement; provisional, not tested. Evidence: skills/performing-content-security-policy-bypass/SKILL.md:L95]
  • Step 4 — Exploit base-uri and Form Action Bypasses [Source statement; provisional, not tested. Evidence: skills/performing-content-security-policy-bypass/SKILL.md:L118]
  • Step 5 — Exploit Nonce and Hash Bypasses [Source statement; provisional, not tested. Evidence: skills/performing-content-security-policy-bypass/SKILL.md:L138]
  • Step 6 — Exploit Data Exfiltration Without script-src [Source statement; provisional, not tested. Evidence: skills/performing-content-security-policy-bypass/SKILL.md:L167]

Limitations & scope

  • Static analysis cannot assess runtime behavior, command success, network reachability, or model output quality.
  • No commands, scripts, network requests, model calls, or controlled skill executions were performed.
  • Category, tags, capabilities, workflows, and bilingual editorial summaries are deterministic candidates pending human review, not verified outcomes.
  • Exact token counts are unavailable until a later pipeline performs and records an official model-specific count.

Relevant for

  • Practitioners evaluating whether to inspect and install the source skill; this audience is inferred from the product context, not measured usage. [Evidence: skills/performing-content-security-policy-bypass/SKILL.md:L1-L33]

What ships with the skill

The file inventory comes from the collected source at the recorded commit. Paths and sizes are structural observations, not a measure of quality.

files
4
Markdown files
2
scripts
1
references
1
Size
37.4 KB
Structural complexity
Low

File inventory

PathTypeBytes
skills/performing-content-security-policy-bypass/LICENSEOther11 KB
skills/performing-content-security-policy-bypass/references/api-reference.mdReference6.5 KB
skills/performing-content-security-policy-bypass/scripts/agent.pyScript11 KB
skills/performing-content-security-policy-bypass/SKILL.mdInstruction9 KB

SKILL.md frontmatter

{
  "name": "performing-content-security-policy-bypass",
  "description": "Analyze Content-Security-Policy headers and bypass them to achieve cross-site scripting by exploiting unsafe-inline/unsafe-eval, whitelisted JSONP endpoints, base-uri and form-action gaps, and nonce/hash weaknesses, then exfiltrate data even without script-src control. Use during web application security assessments or bug bounty hunting when XSS is found but blocked by CSP, or when auditing CSP header configuration for weaknesses.",
  "domain": "cybersecurity",
  "subdomain": "web-application-security",
  "tags": [
    "csp-bypass",
    "content-security-policy",
    "xss",
    "script-injection",
    "nonce-bypass",
    "jsonp",
    "policy-misconfiguration"
  ],
  "version": "1.0",
  "author": "mahipal",
  "license": "Apache-2.0",
  "nist_csf": [
    "PR.PS-01",
    "ID.RA-01",
    "PR.DS-10",
    "DE.CM-01"
  ],
  "mitre_attack": [
    "T1190",
    "T1059.007",
    "T1505.003",
    "T1083",
    "T1055"
  ]
}

A reading of the operating sequence

This workflow reconstructs the apparent sequence from source material. Unless controlled evaluation is explicitly recorded, it is provisional—not an observed trace.

  1. 01
    Decision

    When to Use

    Source-described decision candidate under “When to Use”; not verified execution.

  2. 02
    Action

    Workflow

    Source-described action candidate under “Workflow”; not verified execution.

  3. 03
    Action

    Step 1 — Analyze the CSP Policy

    Source-described action candidate under “Step 1 — Analyze the CSP Policy”; not verified execution.

  4. 04
    Action

    Step 2 — Exploit unsafe-inline and unsafe-eval

    Source-described action candidate under “Step 2 — Exploit unsafe-inline and unsafe-eval”; not verified execution.

  5. 05
    Action

    Step 3 — Exploit Whitelisted Domain JSONP Endpoints

    Source-described action candidate under “Step 3 — Exploit Whitelisted Domain JSONP Endpoints”; not verified execution.

  6. 06
    Action

    Step 4 — Exploit base-uri and Form Action Bypasses

    Source-described action candidate under “Step 4 — Exploit base-uri and Form Action Bypasses”; not verified execution.

Inspect all extracted workflow candidates (17 candidate steps)
  1. 07
    Action

    Step 5 — Exploit Nonce and Hash Bypasses

    Source-described action candidate under “Step 5 — Exploit Nonce and Hash Bypasses”; not verified execution.

  2. 08
    Action

    Step 6 — Exploit Data Exfiltration Without script-src

    Source-described action candidate under “Step 6 — Exploit Data Exfiltration Without script-src”; not verified execution.

  3. 09
    Action

    Key Concepts

    Source-described action candidate under “Key Concepts”; not verified execution.

  4. 10
    Action

    Tools & Systems

    Source-described action candidate under “Tools & Systems”; not verified execution.

  5. 11
    Action

    Common Scenarios

    Source-described action candidate under “Common Scenarios”; not verified execution.

  6. 12
    Action

    JSONP Callback XSS — Exploit JSONP endpoints on whitelisted CDN domains to execute JavaScript callbacks containing XSS payloads

    Source-described action candidate under “Common Scenarios”; not verified execution.

  7. 13
    Input

    AngularJS Sandbox Escape — Load AngularJS from whitelisted CDN and use template injection to bypass CSP script restrictions

    Source-described input candidate under “Common Scenarios”; not verified execution.

  8. 14
    Action

    Nonce Leakage — Extract CSP nonce values through CSS injection or DOM clobbering to inject scripts with valid nonces

    Source-described action candidate under “Common Scenarios”; not verified execution.

  9. 15
    Action

    Base URI Hijacking — Inject base element to redirect all relative script loads to attacker-controlled server

    Source-described action candidate under “Common Scenarios”; not verified execution.

  10. 16
    Output

    Report-Only Exploitation — Identify CSP in report-only mode where violations are logged but not blocked, enabling direct XSS

    Source-described output candidate under “Common Scenarios”; not verified execution.

  11. 17
    Output

    Output Format

    Source-described output candidate under “Output Format”; not verified execution.

Potential risk surfaces

Static findings identify points to inspect before installation. They do not establish that a skill is safe, malicious, or effective.

Attention recommended

68 deterministic lexical finding(s) require review across the collected text. Findings can occur in documentation and do not prove execution or exploitability; binary-only files were not scanned.

Network accessObserved
File writesObserved
Credential useNot observed
Medium

Network access is mentioned

35 occurrences

A URL or network client appears in this source line. Review destinations, data sent, and trust boundaries; static text cannot establish actual network activity. This rule matched 35 location(s) in the collected text; 3 representative location(s) are cited. Matching text may be documentation, and the analyzer did not execute it.

Note

File modification is described or implemented

26 occurrences

This line contains a possible file-write or redirection operation. Check destination paths and overwrite behavior; the static review did not write any file. This rule matched 26 location(s) in the collected text; 3 representative location(s) are cited. Matching text may be documentation, and the analyzer did not execute it.

High

Dynamic command execution is referenced

7 occurrences

A shell, dynamic evaluation, or process execution primitive appears here. Inspect arguments and input control. Presence in source does not prove a command ran. This rule matched 7 location(s) in the collected text; 3 representative location(s) are cited. Matching text may be documentation, and the analyzer did not execute it.

Where context can be spent

Discovery, activation, and resource layers have different meanings. Exact values appear only when the official token-counting method was run with a named model.

Exact token counts unavailable

All token values, including per-file inventory, are null until the pipeline performs an official exact count with an explicit model.

No token measurement was recorded with the required official method. This dossier does not substitute character counts, file sizes, or estimates.

Controlled evaluation

No controlled evaluation

This skill has only the evidence identified above. No task success, token efficiency, latency, or quality advantage is claimed.

Not tested

Use with the source in view

Install command
Inspect the pinned source at https://github.com/mukul975/Anthropic-Cybersecurity-Skills/blob/54a798831d2266a3ca61ce68a7acb80b81160d57/skills/performing-content-security-policy-bypass/SKILL.md and follow the source repository's installation instructions. No installation was performed or verified by this static analyzer. Source license: Apache-2.0.

Prerequisites

  • Static analysis cannot assess runtime behavior, command success, network reachability, or model output quality.
  • No commands, scripts, network requests, model calls, or controlled skill executions were performed.
  • Category, tags, capabilities, workflows, and bilingual editorial summaries are deterministic candidates pending human review, not verified outcomes.
  • Exact token counts are unavailable until a later pipeline performs and records an official model-specific count.

Example prompts

Not provided

A decision, with its limits attached

Strengths

  • The snapshot contains 4 collected file(s), 2 Markdown file(s), and 1 script file(s), enabling source-level inspection. [Evidence: skills/performing-content-security-policy-bypass/SKILL.md:L1]

Considerations

  • No functional, security, or model-quality result has been established. Human review must inspect source context and all cited findings before installation or publication.
Research conclusion

Provisional deterministic static inventory only; pending human editorial review and, separately, controlled evaluation. No install recommendation, security assurance, or effectiveness claim is made.

Traceable by construction

The dossier is a time-bound reading of a public artifact, not an endorsement. Use the source link to inspect the exact upstream material.

mukul975Anthropic-Cybersecurity-Skillsskills/performing-content-security-policy-bypass
Source type
Community
Commit
54a798831d2266a3ca61ce68a7acb80b81160d57
Collected
20 Nov 2026
Last checked
20 Nov 2026
Upstream license
Apache-2.0
Repository stars
36,446
Content basis

Deterministic lexical parsing, YAML frontmatter validation, file inventory, source-described workflow extraction, and heuristic provisional classification of the supplied files only. Generated by machine; no LLM, execution, dynamic testing, or human editorial approval.