XSS scanning method re-vamp

[GoogleCodeExporter]

When scanning for XSS bugs, ZAP replaces the value in the parameter with the 
test string, which in some cases breaks the logic of the webapp. You'll get a 
lot more results by simply re-submitting it with the XSS tag appended to the 
parameter value (in my experience at least).

Example:

 Original:
 site.com/index.php?q=lolcats&page=1

 ZAP:
 site.com/index.php?q=<script>alert("ZAP")</script>&page=1

 Desired behavior:
 site.com/index.php?q=lolcats<script>alert("ZAP")</script>

I've encountered a couple of web-apps where this has been a problem, and is 
causing false negatives, because if I append an attack string onto it, it does 
indeed have a XSS bug. 

Original issue reported on code.google.com by fitblip@gmail.com on 17 Dec 2010 at 11:09

• Merged into: #228

[GoogleCodeExporter]

Original comment by psii...@gmail.com on 18 Dec 2010 at 10:22

• Changed state: Accepted
• Added labels: Type-Enhancement
• Removed labels: Type-Defect

[GoogleCodeExporter]

Original comment by psii...@gmail.com on 7 Jul 2011 at 11:25

• Added labels: AutomatedTools

[GoogleCodeExporter]

Superseded by Issue 228

Original comment by psii...@gmail.com on 7 Nov 2011 at 1:48

• Changed state: Duplicate