I have no idea what you mean.
I'm told the following by the security compliance tech.
The request string used to detect this flaw was:
/bookstore/iwas/?<script>cross_site_scripting.nasl</script>
The output was :
HTTP/1.1 200 OK
Date: Sun, 01 Aug 2010 16:09:59 GMT
Server: Apache mod_fcgid/2.3.5 mod_auth_passthrough/2.1 mod_bwlimited/1.4 FrontPage/5.0.2.2635
Expires: Thu, 19 Nov 1981 08:52:00 GMT
Cache-Control: no-store, no-cache, must-revalidate, post-check=0, pre-check=0
Pragma: no-cache
Set-Cookie: PHPSESSID=7297c80b054a9bdd89abf3d134038e37; path=/
Keep-Alive: timeout=5, max=100
Connection: Keep-Alive
Transfer-Encoding: chunked
Content-Type: text/html
Following is the location of the script in the source code. This is the cross site scripting vulnerability. This is an example and may not be limited simply to this page.
[...]
<!-- InstanceBeginEditable name="body" --> <table width="628" border="1" align="center" cellpadding="0" cellspacing="2" bordercolor="#000000" background="../images/backgrounds/bg-tan-sponge.gif">
<tr>
<td width="628" align="center" valign="top"><form name="WA_eCartBooks_Display" method="POST" action="/bookstore/iwas/index.php?<script>cross_site_scripting.nasl</script>">
<table width="370" cellspacing="0" border="0" cellpadding="5" class="S3C_QuickCartLayout">
<tr>
[...]
Please help me. I'm traveling in the dark. What do I do in non-technical terms?
