iDesign CMS v2.7 - SQL Injection Web Vulnerability

Document Title:
===============
iDesign CMS v2.7 - SQL Injection Web Vulnerability


References (Source):
====================
http://www.vulnerability-lab.com/get_content.php?id=1865


Release Date:
=============
2016-06-29


Vulnerability Laboratory ID (VL-ID):
====================================
1865


Common Vulnerability Scoring System:
====================================
7


Product & Service Introduction:
===============================
https://idesigninc.net


Abstract Advisory Information:
==============================
An independent vulnerability laboratory researcher discovered a remote sql-injection web vulnerability in the official iDesign v2.7 Content Management System.


Vulnerability Disclosure Timeline:
==================================
2016-06-30:	Public Disclosure (Vulnerability Laboratory)


Discovery Status:
=================
Published


Affected Product(s):
====================
iDesign Ltd
Product: iDesign - Content Management System 2.7


Exploitation Technique:
=======================
Remote


Severity Level:
===============
High


Technical Details & Description:
================================
A remote sql injection web vulnerability has been discovered  in the official iDesign v2.7 Content Management System.
The vulnerability allows remote attackers to execute own sql commands to compromise the web-applicaation or connected dbms.

The web vulnerability is located in the `id` and `nid` parameters of the `bio.php` and `article.php` file GET method request. 
Remote attackers are able to execute sql commands by injection of malicious statements via GET method request. The vulnerability 
is located on the application-side and the attack vector is non-persistent. The security vulnerability is a classic order 
by sql injection in the `id` and `nid` value.

The security risk of the sql injection vulnerability is estimated as high with a cvss (common vulnerability scoring system) count of 7.0.
Exploitation of the remote sql injection web vulnerability requires no user interaction or privileged web-application user account.
Successful exploitation of the remote sql injection results in database management system, web-server and web-application compromise.

Request Method(s):
				[+] GET

Vulnerable File(s):
				[+] article.php
				[+] bio.php

Vulnerable Parameter(s):
				[+] id
				[+] nid


Proof of Concept (PoC):
=======================
The remote sql-injection web vulnerability can be exploited by remote attackers without privileged user account or user interaction.
For security demonstration or to reproduce the vulnerability follow the provided information and steps below to continue.

Dork(s):
intext:"Designed and Hosted by iDesign, inc"


PoC: Exploitation
http://localhost:8080/article.php?nid=-[ID]'[SQL-INJECTION VULNERABILITY!]--
http://localhost:8080/bio.php?id=-17%27'[SQL-INJECTION VULNERABILITY!]--


Reference(s):
http://localhost:8080/bio.php
http://localhost:8080/article.php


Solution - Fix & Patch:
=======================
The sql-injection vulnerability can be patched by a secure parse and encode of the vulnerable nid and id parameters in the bio.php or 
article.php file POST method request. Escape and use a prepared statement to secure the sql request in the code-line of the file.


Security Risk:
==============
The security risk of the remote sql-injection web vulnerability in the content management system is estimated as high. (CVSS 7.0)


Credits & Authors:
==================
mr_mask_black - [http://www.vulnerability-lab.com/show.php?user=mr_mask_black]
Greetz: T3NZ0G4N - arshia danger - Sir.h4m1d - pEyMan - hossein - kian error - king dawn - white wolf - king of peace and all friends ...


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]™