Introducing: Wingman
Wingman is an XSS scanner designed for bug bounty hunters, infosec professionals, and hobbyists.
Read more:
https://t.co/Prf9CpHjQj
@mayank98108 The errors are generated by the Google Chrome driver, but don't cause any functional issues. Unfortunately, for now, the only way to get rid of them is to manually redirect them to /dev/null (or "nul" on windows it looks like):
https://t.co/ozXTdPPNRx
@KN0X55@rub003@IamRenganathan Yes, a single request works 99% of the time. There are indeed some applications that will reject them. (Un)fortunately, those endpoints will be unexploitable since any characters you might need to create a valid payload are blocked anyway.
@KN0X55@rub003@IamRenganathan Using a browser to verify is fair, but not actually necessary if the underlying logic is solid. Wingman can determine whether something is vulnerable or not in a single request. In my case, false positives are very common and can usually be traced back to some kind of bug.🙂
@shadow00hunter1@ofjaaah You're welcome! Mainly because HTTP or HTTPS might not serve the same webpage, happens more often than you'd think. I'd say it's better this way since what you give is always what you get.
@shadow00hunter1@ofjaaah Hi, it actually means it finished crawling. You can try running with verbose mode enabled (-v) to unsilence HTTP errors if you think something is wrong.
@Blue_CanaryBE Noted, thanks! There should definitely be a flag to mute the sink logger, since there isn't one right now. However, even though it's not ideal, you can still filter the output with jq
@theXSSrat@knoxss_me @sam25889936 To be fair Wingman can do exactly that (and more). If you watch the video completely you'll see that it hooks into your Chrome browser rather than relying on an extension:
https://t.co/htiagfpaUb