s0md3v/XSStrike
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Added contribution & license section

Browse Source
This commit is contained in:
Somdev Sangwan
2018-10-27 19:18:02 +05:30
committed by GitHub
parent a2f2602d7a
commit 6242bca8fb
1 changed files with 9 additions and 2 deletions
Download Patch File Download Diff File Expand all files Collapse all files

11
README.md
View File

@@ -24,13 +24,13 @@
<p align="center">
<a href="https://github.com/s0md3v/XSStrike/wiki">XSStrike Wiki</a> •
<a href="https://github.com/s0md3v/XSStrike/wiki/Usage">How To Use</a> •
<a href="https://github.com/s0md3v/XSStrike/wiki/Usage">Usage</a> •
<a href="https://github.com/s0md3v/XSStrike/wiki/Compatibility-&-Dependencies">Compatibility</a> •
<a href="https://github.com/s0md3v/XSStrike#gallery">Gallery</a>
</p>
### Why XSStrike?
Every XSS scanner out there has a list of payloads, it injectes the payloads and if the payload is reflected into the webpage, it is declared vulnerable but that's just stupid. XSStrike on the other hand analyses the response with multiple parsers and then crafts payloads that are guaranteed to work.
Every XSS scanner out there has a list of payloads, they inject the payloads and if the payload is reflected into the webpage, it is declared vulnerable but that's just stupid. XSStrike on the other hand analyses the response with multiple parsers and then crafts payloads that are guaranteed to work.
Here are some examples of the payloads generated by XSStrike:
```
}]};(confirm)()//\
@@ -64,3 +64,10 @@ Apart from that, XSStrike has crawling, fuzzing, WAF detection capabilities as w
![arjun](https://image.ibb.co/bOAD5q/Screenshot-2018-10-27-18-16-37.png)
#### Interactive HTTP Headers Prompt
![headers](https://image.ibb.co/jw5NgV/Screenshot-2018-10-27-18-45-32.png)
### Contribution & License
XSStrike v.30 is in beta phase and has been released for public testing.<br>
Useful issues and pull requests are appreciated.
I haven't decided a license yet.