XSS scanning method re-vamp

[zapbot]

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 on 2010-12-17 23:09:23

[zapbot]

(No text was entered with this change)

Original issue reported on code.google.com by psiinon on 2010-12-18 10:22:02

• Labels added: Type-Enhancement
• Labels removed: Type-Defect

[zapbot]

(No text was entered with this change)

Original issue reported on code.google.com by psiinon on 2011-07-07 11:25:06

• Labels added: AutomatedTools

[zapbot]

Superseded by Issue 228

Original issue reported on code.google.com by psiinon on 2011-11-07 13:48:00

[lock]

This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.