-
Notifications
You must be signed in to change notification settings - Fork 23.9k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
XSS fuzz lists #40
Comments
I agree, but the context in that file is advantageous. How about make a stand alone fuzzing version and commit with a comment that one is better consumed by Burp and the other used as a reference? |
Yes please! |
Yes, that's a good idea. We should mark files as tool-ready or something within the name of the list. |
@danielmiessler @jhaddix I realize this issue is a little old, but I came across it today and thought the idea here is fabulous. I'd be happy to take a stab at this, that is, if you still want something. Is the solution you want really just make new fuzzing files that can be directly imported into tools (Burp and ZAP come to mind)? |
Sounds like a good idea to me! |
Great idea. |
This is a great idea. |
@g0tmi1k I think this can be closed |
Many of the XSS payload files are not directly consumable by fuzzing applications, such as Burp Intruder. I think it would be great if there were seperate fuzzing files to the discussion files. For example, Mario's XSS file is AWESOME and so advanced that it's akin to magic, but it takes a bit of work to use within tools.
How best to help you guys with this?
The text was updated successfully, but these errors were encountered: