hunt-xss

Detect and validate reflected, stored, and DOM-based XSS vulnerabilities on web targets.

Updated May 29, 2026
One-click install
npx skills add https://github.com/hhjkjkjk/Claude-skills --skill hunt-xss-hhjkjkjk
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: hunt-xss
Source: https://github.com/hhjkjkjk/Claude-skills/tree/main/skills/hunt-xss
Command: npx skills add https://github.com/hhjkjkjk/Claude-skills --skill hunt-xss-hhjkjkjk

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Finding XSS vulnerabilities requires knowing where user input reflects, how sanitizers fail, and how to prove real impact instead of submitting false positives that get rejected. This Skill provides a structured hunting methodology built from 174 public bug bounty reports so testers can systematically identify, confirm, and chain XSS findings. ## Core Features & Use Cases - Systematic Hunting Methodology: A 12-step workflow covering reflection mapping, sanitizer probing with unique canary markers, SVG upload vectors, markdown renderer injection, redirect parameters, and cache poisoning. - Payload & Bypass Library: Ready-to-use payloads for attribute escapes, mXSS sanitizer bypasses (math+style, svg+style), CSP bypasses, WAF evasion, and grep patterns for source review. - Validation Gates: OOB confirmation rules for blind/stored XSS using Collaborator beacons, plus a Gate 0 checklist to prove concrete impact before reporting. - Use Case: While testing a target's wiki feature, use the markdown and Kroki diagram injection payloads to plant a stored XSS, confirm execution via an out-of-band callback, then chain it to demonstrate admin session theft for a higher-severity report. ## Quick Start Use the hunt-xss skill to map reflection points on my target and test them with sanitizer bypass payloads.

Frequently Asked Questions about hunt-xss

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

FAQPage Schema
How do I find XSS vulnerabilities on a web target?▼

Map every reflection point by spidering the target, then classify each as reflected, stored, or DOM-based. Probe with a unique random canary string to see which characters are escaped, then apply context-appropriate payloads for HTML, attribute, or JavaScript sinks.

How to confirm blind or stored XSS without a visible alert?▼

Plant out-of-band beacons using a unique Collaborator subdomain in fields viewed later by admins, such as error messages, User-Agent headers, or login usernames. A callback from a browser User-Agent to your listener confirms execution; encoded output in the response does not.

Can SVG file uploads bypass CSP for XSS?▼

Yes. SVG files can contain script tags, and Content-Security-Policy often applies to HTML responses but not to image/svg+xml responses. If the SVG is served same-origin, the executing JavaScript gains full session cookie and API access.

Why does my XSS payload show in the response but not execute?▼

If your payload appears HTML-encoded (like <script>) or URL-encoded inside an attribute, the output is correctly escaped and it is not XSS. Verify with a unique marker that the reflection is unencoded and test in a real browser, since Burp results can differ from Chrome.

What makes an XSS report get rejected or downgraded?▼

Reports fail when the canary appears naturally in the page, the payload only fires in the attacker's own session (self-XSS), or no concrete impact is demonstrated. Show what the attacker can do, what the victim loses, and provide a PoC reproducible in a current browser within 10 minutes.