WordPress Scoreme Theme Cross Site Scripting

`  
Document Title:  
===============  
Wordpress Scoreme Theme - Client Side Cross Site Scripting Web Vulnerability  
  
  
References (Source):  
====================  
http://www.vulnerability-lab.com/get_content.php?id=1808  
  
  
Release Date:  
=============  
2016-04-01  
  
  
Vulnerability Laboratory ID (VL-ID):  
====================================  
1808  
  
  
Common Vulnerability Scoring System:  
====================================  
3  
  
  
Product & Service Introduction:  
===============================  
ScoreMe is a dynamic and flexible WordPress theme. The layout of the  
this WordPress theme is clean and minimal like modern creative themes.  
The theme is a magazine style for those who want to make a website about  
preview, reviews and news. ScoreMe has rating system for that.  
  
(Copy of the Homepage:   
http://www.wordpressfolio.com/blogmagazine-themes/scoreme-magazine-wordpress-theme-with-ratings/  
)  
  
  
Abstract Advisory Information:  
==============================  
An independent vulnerability laboratory researcher discovered a cross  
site scripting vulnerabilities in the Wordpress Scoreme Theme.  
  
  
Vulnerability Disclosure Timeline:  
==================================  
2016-04-01: Public Disclosure (Vulnerability Laboratory)  
  
  
Discovery Status:  
=================  
Published  
  
  
Affected Product(s):  
====================  
  
Exploitation Technique:  
=======================  
Remote  
  
  
Severity Level:  
===============  
Medium  
  
  
Technical Details & Description:  
================================  
A cross site scripting web vulnerability has been discovered in the  
official Wordpress Scoreme Theme web-application.  
The vulnerability allows remote attackers to inject malicious script  
codes on the client-side of the affected web-application.  
  
The vulnerability is located in the `s` value of the `index.php` file.  
Remote attackers are able to inject own malicious script  
codes to the client-side of the affected web-application. The request  
method to inject is GET and the attack vector is client-side.  
  
The security risk of the client-side web vulnerability is estimated as  
medium with a cvss (common vulnerability scoring system) count of 3.0.  
Exploitation of the non-persistent cross site scripting vulnerability  
requires low privileged web-application user account and low user  
interaction.  
Successful exploitation results in session hijacking, persistent  
phishings attacks, persistent external redirect and malware loads or  
persistent  
manipulation of affected or connected module context.  
  
Request Method(s):  
[+] GET  
  
Vulnerable File(s):  
[+] index.php  
  
Vulnerable Parameter(s):  
[+] s  
  
  
Proof of Concept (PoC):  
=======================  
The vulnerability can be exploited by remote attackers without a low  
privileged or restricted user account and with low user interaction.  
For security demonstration or to reproduce the vulnerability follow the  
provided information and steps below to continue.  
  
PoC: Example  
http://localhost:8080/wordpress/?s=[CLIENT SIDE CROSS SITE SCRIPTING  
VULNERABILITY!]  
  
PoC: Exploitation  
http://localhost:8080/wordpress/?s="/><script>alert(/XSS By 0x3a/);</script>  
  
  
Solution - Fix & Patch:  
=======================  
The vulnerability can be patched by a secure parse and encode of the  
vulnerable `s` value in the index.php GET method request.  
Disallow usage of special chars and filter to prevent client-side script  
code injection attacks against the web-application module.  
  
  
Security Risk:  
==============  
The security risk of the application-side cross site scripting web  
vulnerabilities in the wordpress plugin are estimated as medium. (CVSS 3.0)  
  
  
Credits & Authors:  
==================  
Iran Cyber Security Group - 0x3a (ICG SEC) [Iran-Cyber.Net]  
[http://www.vulnerability-lab.com/show.php?user=Iran%20Cyber%20Security]  
Special Tnx 2 : MOHAMAD_NOFOZI , root3r , Sir.H4m1d , 0day , pi.hack ,  
s4jj4d , whitewolf , jok3r , MoHaMaD-BlAcK , l3gi0n, mr.turk , 0xdevil ,  
king_k4li  
  
  
  
Disclaimer & Information:  
=========================  
The information provided in this advisory is provided as it is without  
any warranty. Vulnerability Lab disclaims all warranties, either  
expressed or implied,  
including the warranties of merchantability and capability for a  
particular purpose. Vulnerability-Lab or its suppliers are not liable in  
any case of damage,  
including direct, indirect, incidental, consequential loss of business  
profits or special damages, even if Vulnerability-Lab or its suppliers  
have been advised  
of the possibility of such damages. Some states do not allow the  
exclusion or limitation of liability for consequential or incidental  
damages so the foregoing  
limitation may not apply. We do not approve or encourage anybody to  
break any licenses, policies, deface websites, hack into databases or  
trade with stolen data.  
  
Domains: www.vulnerability-lab.com - www.vuln-lab.com   
- www.evolution-sec.com  
Contact: [email protected] -  
[email protected] - [email protected]  
Section: magazine.vulnerability-lab.com -  
vulnerability-lab.com/contact.php -  
evolution-sec.com/contact  
Social: twitter.com/vuln_lab -  
facebook.com/VulnerabilityLab -  
youtube.com/user/vulnerability0lab  
Feeds: vulnerability-lab.com/rss/rss.php -  
vulnerability-lab.com/rss/rss_upcoming.php -  
vulnerability-lab.com/rss/rss_news.php  
Programs: vulnerability-lab.com/submit.php -  
vulnerability-lab.com/list-of-bug-bounty-programs.php -  
vulnerability-lab.com/register.php  
  
Any modified copy or reproduction, including partially usages, of this  
file requires authorization from Vulnerability Laboratory. Permission to  
electronically  
redistribute this alert in its unmodified form is granted. All other  
rights, including the use of other media, are reserved by  
Vulnerability-Lab Research Team or  
its suppliers. All pictures, texts, advisories, source code, videos and  
other information on this website is trademark of vulnerability-lab team  
& the specific  
authors or managers. To record, list, modify, use or edit our material  
contact (admin@ or [email protected]) to get a ask permission.  
  
Copyright © 2016 | Vulnerability Laboratory -  
[Evolution Security GmbH]™  
  
--   
VULNERABILITY LABORATORY - RESEARCH TEAM  
SERVICE: www.vulnerability-lab.com  
CONTACT: [email protected]  
  
`