xss-reflected-hunter

Detect reflected XSS by tracing input through redirects, Markdown renderers, and CSP-sensitive sinks.

1|Updated Aug 11, 2026
One-click install
npx skills add https://github.com/Maybe4a6f7365/agentic-bug-bounty-framework --skill xss-reflected-hunter-maybe4a6f7365
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: xss-reflected-hunter
Source: https://github.com/Maybe4a6f7365/agentic-bug-bounty-framework/tree/main/skills/xss-reflected-hunter
Command: npx skills add https://github.com/Maybe4a6f7365/agentic-bug-bounty-framework --skill xss-reflected-hunter-maybe4a6f7365

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires requests.

What problem does it solve? Reflected XSS testing often produces false positives from raw reflection that never executes, or misses context-specific sinks hidden behind redirects, Markdown renderers, and media proxies. This Skill provides a disciplined method to trace attacker-controlled input to a real executable sink and prove target-origin execution before reporting. ## Core Features & Use Cases - Context-driven payload selection: Send inert canaries through query, path, form, and redirect parameters, then derive minimal payloads matching the observed sink (HTML text, attribute, URL navigation, path segment). - Advanced sink coverage: Test Markdown URL sinks, HEAD/GET validation mismatches in media proxies, and CSP nonce/allowlist gadget chains after proving injection. - Negative-control discipline: Apply eight categorized stop conditions (expected behavior, self-XSS, out-of-scope assets, patched versions) so unverifiable or below-threshold findings are never filed. - Use Case: During a bug-bounty engagement, you notice a returnTo parameter reflected in a post-login Continue action. Use this Skill to confirm a javascript: navigation payload executes under the target origin in a clean browser session, then document the DOM, CSP, and interaction prerequisites for the report. ## Quick Start Use the xss-reflected-hunter skill to test the returnTo parameter on the target's login confirmation page for reflected XSS with a console canary.

Frequently Asked Questions about xss-reflected-hunter

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

FAQPage Schema
How do I test for reflected XSS in a web application?

Send a unique inert canary through every query, path, form, and redirect parameter, then record the exact reflection context. Reproduce in a real browser and use only the minimal payload matching the observed sink, since raw reflection without execution is not XSS.

What is the difference between reflected and stored XSS testing?

Reflected XSS executes when input returns immediately in the response, while stored XSS persists and renders later. This Skill covers reflected cases; use a stored-XSS hunter when the input is saved server-side and rendered in a later view.

Why is raw reflection in a response not enough to report XSS?

Reflection only proves data round-tripped, not that a parser converts it into executable DOM. You must demonstrate a browser canary executing with location.origin equal to the target, ruling out extensions, sandboxed previews, or attacker origins.

Can a CSP bypass alone be reported as reflected XSS?

No. CSP bypass without a proven injection sink is defense-in-depth weakness, not XSS. Only evaluate CSP chains, such as allowlisted script gadgets with nonce reuse, after confirming an HTML injection point exists.

When should I stop and not file a reflected XSS finding?

Stop when input is properly encoded, execution requires self-XSS or DevTools pasting, the sink runs on a data: or attacker origin, the asset is out of scope, or the deployed sanitizer version already patches the bypass per the OSV/GHSA version table.