xss-html-injection

Tests web applications for XSS and HTML injection vulnerabilities across stored, reflected, and DOM-based vectors.

Updated Aug 11, 2026
One-click install
npx skills add https://github.com/DucCuong159/Realtime-chatapp --skill xss-html-injection-duccuong159
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: xss-html-injection
Source: https://github.com/DucCuong159/Realtime-chatapp/tree/main/.agent/skills/xss-html-injection
Command: npx skills add https://github.com/DucCuong159/Realtime-chatapp --skill xss-html-injection-duccuong159

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Web applications that fail to sanitize user input are exposed to cross-site scripting and HTML injection attacks that enable session hijacking, credential theft, and content manipulation. This Skill provides a systematic workflow to detect, classify, and demonstrate these client-side injection flaws during authorized security assessments. ## Core Features & Use Cases - Multi-Vector Detection: Identify stored, reflected, and DOM-based XSS by probing input reflection points, dangerous JavaScript sinks, and user-controllable sources. - Exploitation Demonstrations: Craft proof-of-concept payloads for cookie theft, keylogging, phishing form injection, and session hijacking in controlled environments. - Filter Bypass Techniques: Apply encoding variations, tag obfuscation, and CSP bypass methods to validate the robustness of input sanitization and output encoding. - Use Case: During an authorized pentest of a web application, use this Skill to test a comment feature for stored XSS, confirm script execution, document the impact with a controlled payload, and produce remediation recommendations including CSP configuration. ## Quick Start Ask the AI to assess a specific authorized target URL for XSS and HTML injection vulnerabilities, confirming written authorization and scope first.

Frequently Asked Questions about xss-html-injection

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

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

XSS testing starts by identifying input reflection points such as search boxes, profile fields, and URL parameters, then inserting probe payloads like script tags and event handlers. Monitor responses for unencoded reflection and JavaScript execution to confirm exploitability.

What is the difference between stored, reflected, and DOM-based XSS?

Stored XSS persists in a database and affects all viewers of the content. Reflected XSS appears only in the immediate response to a crafted request. DOM-based XSS executes entirely in the browser when client-side JavaScript processes user-controlled input.

How to bypass XSS filters and WAF protections?

Filter bypass techniques include case variation in tags, HTML entity and hex encoding, malformed tag syntax, JavaScript obfuscation with template literals or constructors, and whitespace or comment insertion. CSP bypasses may use JSONP endpoints on whitelisted domains.

Why is my XSS payload not executing in the browser?

Payloads fail when Content Security Policy blocks inline scripts, output encoding neutralizes special characters, or the payload lands in the wrong context. Check CSP headers, try event-handler vectors like img onerror, and break out of attribute contexts with quotes.

Can XSS steal cookies protected by HttpOnly?

HttpOnly cookies cannot be accessed via document.cookie in JavaScript, blocking direct theft. Attackers may instead target localStorage, sessionStorage, or perform actions as the victim, so assessments should test all client-side storage mechanisms.

Is authorization required before XSS testing?

Yes, written authorization from the system owner is mandatory before any XSS testing. The scope must define target domains and features, and any captured session data must be handled per agreed data protection procedures.