Message-ID: <564B2979.9090703@vulnerability-lab.com>
Date: Tue, 17 Nov 2015 14:19:53 +0100
From: Vulnerability Lab <research@...nerability-lab.com>
To: fulldisclosure@...lists.org
Subject: [FD] Murgent CMS - SQL Injection Vulnerability

Document Title:
===============
Murgent CMS - SQL Injection Vulnerability


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


Release Date:
=============
2015-11-16


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


Common Vulnerability Scoring System:
====================================
8.2


Product & Service Introduction:
===============================
http://murgent.com/


Abstract Advisory Information:
==============================
An independent vulnerability laboratory researcher discovered a remote sql injection web vulnerability in the official Murgent Content Management System 2015Q4.


Vulnerability Disclosure Timeline:
==================================
2015-11-16: Public Disclosure (Vulnerability Laboratory)


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


Affected Product(s):
====================

Exploitation Technique:
=======================
Bulletins


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


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

The vulnerability is located in the `id` value of the `index.php` and `view-event.php` file. Remote attackers are able to execute 
own sql commands by manipulation of the GET method request with the vulnerable id parameter. The request method to inject the sql 
command is GET and the issue is located on the application-side of the online-service. The sql vulnerability allows remote attackers 
to compromise the database management system that is connected to the web-application.

The security risk of the sql injection vulnerability is estimated as high with a cvss (common vulnerability scoring system) count of 8.2.
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):
						[+] index.php
						[+] view-event.php

Vulnerable Parameter(s):
						[+] action > preview &id


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


Google Dork(s):
intext:"Developed by murgent" inurl:"id="
intext:"Powered by murgent" inurl:"id="


PoC:
http://localhost:8080/view-event.php?id=569%27[SQL-INJECTION VULNERABILITY!]
https://localhost:8080/index.php?action=preview&id=21891%27[SQL-INJECTION VULNERABILITY!]


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


Credits & Authors:
==================
Sia Turk - GuardIran Digital Security Team
Special Thanks to: Yashar-Turk,Ehsan Gomnam,Mr.3okoT,Mr.RezaRabet,Night-Wolf, C0d3!Nj3ct!0N,DeMoN,Yasin-Turk,Pesar Shab,Sia Turk and All Of My 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 vendor licenses, 
policies, deface websites, hack into databases or trade with fraud/stolen material.

Domains:    www.vulnerability-lab.com   	- www.vuln-lab.com			       		- www.evolution-sec.com
Contact:    admin@...nerability-lab.com 	- research@...nerability-lab.com 	       		- admin@...lution-sec.com
Section:    magazine.vulnerability-db.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/

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 (feed), modify, use or edit our material contact 
(admin@...nerability-lab.com or research@...nerability-lab.com) to get a permission.

				Copyright © 2015 | Vulnerability Laboratory - [Evolution Security GmbH]™



-- 
VULNERABILITY LABORATORY - RESEARCH TEAM
SERVICE: www.vulnerability-lab.com
CONTACT: research@...nerability-lab.com
PGP KEY: http://www.vulnerability-lab.com/keys/admin@vulnerability-lab.com%280x198E9928%29.txt



_______________________________________________
Sent through the Full Disclosure mailing list
https://nmap.org/mailman/listinfo/fulldisclosure
Web Archives & RSS: http://seclists.org/fulldisclosure/

Powered by blists - more mailing lists