Reflected Cross-Site Scripting (XSS) Vulnerability
Posted: Tue May 19, 2015 10:14 pm
I had a security scan done on my FormaLMS and received a Reflected Cross-Site Scripting from the forgot password screen:
Evidence:
URL: https://24.106.122.83/index.php
Parameter: modname
Request: GET
/index.php?modname=<script>alert('TK000000BD')</script>&op=lostpwd
HTTP/1.1
Accept: */*
User-Agent: Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.1)
Host: 24.106.122.83
Content-Type: text/html
Content-Length: 0
Response: HTTP/1.1 200 OK
Content-Type: text/html; charset=utf-8
Server: Microsoft-IIS/7.5
X-Powered-By: PHP/5.6.6
Set-Cookie: docebo_session=6j914tgd03dtbi556j2k3kdst4; path=/
X-Powered-By: ASP.NET
Date: Mon, 18 May 2015 13:56:40 GMT
Content-Length: 6835
Evidence: <script>alert('TK000000BD')</script>
Remediation:
Before accepting any user-supplied data, the application should
validate this data's format and reject any characters that are not explicitly
allowed (i.e. a white-list). This list should be as restrictive as possible.
Before using any data (stored or user-supplied) to generate web page
content, the application should escape all non alpha-numeric characters
(i.e. output-validation). This is particularly important when the original
source of data is beyond the control of the application. Even if the source of
the data isn't performing input-validation, output-validation will still prevent
XSS.
Can anyone address this? I am running FormaLMS 1.4
Evidence:
URL: https://24.106.122.83/index.php
Parameter: modname
Request: GET
/index.php?modname=<script>alert('TK000000BD')</script>&op=lostpwd
HTTP/1.1
Accept: */*
User-Agent: Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.1)
Host: 24.106.122.83
Content-Type: text/html
Content-Length: 0
Response: HTTP/1.1 200 OK
Content-Type: text/html; charset=utf-8
Server: Microsoft-IIS/7.5
X-Powered-By: PHP/5.6.6
Set-Cookie: docebo_session=6j914tgd03dtbi556j2k3kdst4; path=/
X-Powered-By: ASP.NET
Date: Mon, 18 May 2015 13:56:40 GMT
Content-Length: 6835
Evidence: <script>alert('TK000000BD')</script>
Remediation:
Before accepting any user-supplied data, the application should
validate this data's format and reject any characters that are not explicitly
allowed (i.e. a white-list). This list should be as restrictive as possible.
Before using any data (stored or user-supplied) to generate web page
content, the application should escape all non alpha-numeric characters
(i.e. output-validation). This is particularly important when the original
source of data is beyond the control of the application. Even if the source of
the data isn't performing input-validation, output-validation will still prevent
XSS.
Can anyone address this? I am running FormaLMS 1.4