scans for different types of XSS on a list of URLs
XSS Searcher is the extended version based on the initial idea already published as “xssfinder”. This private version allows an attacker to perform not only GET but also POST requests. Additionally, it’s possible to proxy every request through Burp or another tunnel.
Rename the example.app-settings.conf to app-settings.conf and adjust the settings. It should work out of the box but depending on the target I would recommend resizing the chunk sizes.
This tool does not expect any arguments via CLI, so just type:
It’s possible to set a lot of options and settings, so here are some explanations.
The main config file is the “app-settings.conf”, everything has to be done in that file! Besides that, there are some other files that allow setting more complex data like headers, URLs and cookies.
Use this file to add a cookie string. I usually copy the one which you can see in every burp request. Please just copy the value of the “Cookie:”-header. Sample input is in the default file.
This file defines the HTTP headers which are added to the request and manipulated (payload is added to each one). The most important ones are already in the file. But feel free to add more.
The tool has the option to brute force get and post parameters. In that case, those parameters (+ those in the query string) will be used. Each parameter gets the payload as value. Most important are already in that file.
That’s the file you need! Please add here your links to scan. The following formats are allowed:
- https:// domain .com
- https:// domain. com/path
- https:// domain. com/path? param=value¶m1=value1
- domain. com
When the last case is detected an “http://” is prepended. This tool is intended to work with a good list of URLs. A good way to get one is to just export it using burp. Then you have a valid list of URLs. All you need to do ist to just add your cookies.
This is the log folder where everything gets logged to!
The app-settings.conf defined the program workflow. Its the most important file, you can activate/deactivate different modules there.
Some requests can take longer. Here you can define the max. the execution time of one request. I recommend the values between 2 and 6 seconds.
The more threads, the faster the script is – but since we are dealing with a lot of connections I usually keep this below 10 on my personal computer and around 30 on my VPS.
Setting this to true will result in only “base requests” – this means the URL lists are just spidered and interesting parameters extracted. You could use that to fill your burp sitemap quickly.
Use can skip POST requests setting this to “false”
This is similar – skip GET requests if set to “false”
Attack type settings
How many GET parameters to test with one request?
How many POST parameters to test with one request?
Its also possible to use a tunnel, e.g. “127.0.0.1 :8080” (Burp Proxy), to monitor all traffic within Burp.
Setting this to “true” will force the script to use a tunneled connection.
Set here your proxy server “ip:port”.
The result is the following one when you open Burp you can watch your HTTP history:
Please just create an issue and tag it as a feature request.