hunt-xss

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

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/AKasem1/claude-bug-bounty --skill hunt-xss
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: hunt-xss
Source: https://github.com/AKasem1/claude-bug-bounty/tree/main/skills/hunt-xss
Command: npx skills add https://github.com/AKasem1/claude-bug-bounty --skill hunt-xss

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Hunting cross-site scripting (XSS) vulnerabilities wastes time on false positives and weak validation, especially for reflected, stored, and DOM-based cases where impact depends on where the payload executes.

Core Features & Use Cases

  • Crown-jewel targeting guidance: Prioritizes high-payout XSS surfaces like admin panels, sign-in/SSO flows, stored-rendering contexts, and payout/financial pages.
  • OOB confirmation methodology: Provides strict rules for when blind/stored XSS claims are valid, including collaborator-based proof requirements and what to treat as non-confirmation.
  • Attack-surface driven workflow: Maps common XSS signals (URL patterns, response headers, DOM sinks, sanitizer/root-cause patterns) into a step-by-step hunting process that ends with browser validation.
  • Context-appropriate payload strategy: Includes reflection markers, sanitizer probing, sanitizer-bypass techniques (including SVG and math/style mXSS), redirect/UTM testing, and cache-poisoning considerations.
  • Chain references to adjacent skills: Links XSS to cache poisoning, CSRF exploitation via stored XSS, and HTTP request smuggling scenarios to help plan higher-impact reports.

Quick Start

Run the hunt on a new target by using a browser-safe XSS canary first, map reflection points, then validate the highest-value sinks with collaborator-based confirmation where needed.

Frequently Asked Questions about hunt-xss

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

FAQPage Schema
How do I validate stored and reflected XSS vulnerabilities for bug bounty reports?

XSS payload testing for admin interfaces requires mapping reflection points with browser-safe canaries and applying context-appropriate payloads. You must match payloads to specific HTML, attribute, JavaScript, or URL execution contexts to bypass sanitizers effectively.

What is the best way to confirm blind stored XSS without false positives?

The best way to confirm blind stored XSS is using out-of-band collaborator-based proof requirements. Treat non-confirmation cases strictly, ensuring that payload execution in high-value surfaces like admin panels is verified through reliable interaction callbacks.

How do I bypass Content Security Policy and sanitizers during XSS hunting?

To bypass CSP and sanitizers during XSS hunting, apply context-appropriate payload strategies including SVG and math/style mXSS techniques. Match these payloads to the exact HTML, attribute, or JS context where reflection occurs to achieve successful execution.

Can I use XSS hunting techniques to test redirect and UTM parameters?

Yes, you can test redirect and UTM parameters for XSS by mapping common DOM sinks and URL patterns. The hunting process includes specific redirect and UTM testing methodologies, along with cache-poisoning considerations for cached pages.

When should I chain XSS with other web security vulnerabilities like cache poisoning?

You should chain XSS with cache poisoning, CSRF exploitation, or HTTP request smuggling when planning higher-impact reports. Targeting crown-jewel surfaces like financial pages and SSO flows maximizes vulnerability severity and bug bounty payouts.