What problem does it solve?
DOM-based XSS occurs entirely in the browser — inputs controlled by the user flow from a JavaScript source into a dangerous sink without server-side reflection. Standard curl-based testing cannot detect it; browser-based testing is required.
Core Features & Use Cases
- DOM XSS testing covers source/sink analysis, client-side template injection (CSTI), AngularJS expression injection, postMessage exploitation, DOM clobbering, and browser-based detection techniques.
- Step-by-step workflows include source discovery, framework detection (AngularJS, Vue.js, jQuery), CSTI payloads, and advanced techniques such as mXSS and CSP-bypass strategies.
- Real-world use cases include validating client-side vulnerabilities in SPAs and libraries, designing defensive controls, and producing repeatable test results.
Quick Start
Open a target web page in a browser, identify untrusted input sources such as URL hash, query parameters, and postMessage, then apply the documented DOM XSS payloads to confirm the presence and behavior of sinks.