ITAS Team found out XSS vulnerability in articleFR CMS

Cross-Site Scripting (XSS) attacks are a type of injection, in which malicious scripts are injected into otherwise benign and trusted web sites. XSS attacks occur when an attacker uses a web application to send malicious code, generally in the form of a browser side script, to a different end user. Flaws that allow these attacks to succeed are quite widespread and occur anywhere a web application uses input from a user within the output it generates without validating or encoding it.
An attacker can use this vulnerability to send a malicious script to an unsuspecting user. The end user’s browser has no way to know that the script should not be trusted, and will execute the script. Because it thinks the script came from a trusted source, the malicious script can access any cookies, session tokens, or other sensitive information retained by the browser and used with that site. These scripts can even rewrite the content of the HTML page.
The articleFR CMS got user’s input data without properly sanitizing the request from the parameter q, so the Reflected Cross-Site Scripting occurred.

Vulnerability information:

– Vulnerability: Reflected Cross-Site Scripting
– Vendor:
– Download link:
– Affected version: version 3.0.5
– CVE ID: CVE-2015-1363
– Author: Tran Dinh Tien ( & ITAS Team


GET /demo/search/v/?q=%3Cscript%3Ealert%28%27XSS%27%29%3C%2Fscript%3E HTTP/1.1
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:35.0) Gecko/20100101 Firefox/35.0
Accept: text/html,application/xhtml+xml,application/xml;q=0.9,*/*;q=0.8
Accept-Language: en-US,en;q=0.5
Accept-Encoding: gzip, deflate
Cookie: lhc_per={%22vid%22:%226dq7k8utakegpenguv2s%22}; _ga=GA1.2.1982695316.1420692931; __unam=ba3cbfe-14ac7e5c29b-63911eb3-7; PHPSESSID=207352ef26262a6aab50e55f77cda2f3; _gat=1
Connection: keep-alive

Information disclosure:
+ 12/09/2014: Contact to vendor – vendor did not reply
+ 12/11/2014: Contact to vendor – vendor did not reply
+ 12/22/2014: Contact to vendor – vendor replied
+ 12/23/2014: Send the detail vulnerability to vendor – vendor did not reply
+ 01/22/2015: Public information


/ Blog / Tags: , ,

Share the Post