Title: ====== 7sepehr CMS 2012 - Multiple SQL Injection Vulnerabilities Date: ===== 2012-08-12 References: =========== http://www.vulnerability-lab.com/get_content.php?id=679 VL-ID: ===== 680 Common Vulnerability Scoring System: ==================================== 8.3 Abstract: ========= The Laboratory Researcher (Nafsh) Ehram Shahmohamadi (sec-lab.ir) discovered multiple SQL Injection Vulnerabilities in the 7sepehr CMS. Report-Timeline: ================ Vulnerability Laboratory [Research Team] - Ibrahim El-Sayed [storm] (strom@xxxxxxxxxxxxxxxxxxxxx) Status: ======== Published Exploitation-Technique: ======================= Remote Severity: ========= Critical Details: ======== Multiple SQL Injection vulnerabilities are detected in the official 7sepehr.com Content Management System 2012. Remote attackers can execute/inject own sql commands to compromise the affected application dbms. The vulnerabilities are located in the news_detail, news_view and content asp modules with the bound vulnerable id parameter. Successful exploitation of the remote sql injection vulnerability result in dbmsor web application compromise. Vulnerable File(s): [+] news_Detail.asp [+] newsview.asp [+] contents.aspx Vulnerable Parameter(s): [+] id Proof of Concept: ================= The remote sql injection vulnerabilities can be exploited by remote attackers without privileged user account & without required user inter action. For demonstration or reproduce ... Dork: `Powered by 7sepehr.com` PoC: http://127.0.0.1:1338/news/news_Detail.asp?id=-1 union all select [SQL INJECTION VULNERABILITY]-- http://127.0.0.1:1338/news/newsview.asp?id=-1 union all select [SQL INJECTION VULNERABILITY]-- http://127.0.0.1:1338/contents.aspx?id=-1 union all select [SQL INJECTION VULNERABILITY]-- Risk: ===== The security risk of the remote sql injection vulnerabilities are estimated as critical. Credits: ======== Nafsh - Ehram Shahmohamadi - (research@xxxxxxxxxx) [www.sec-lab.ir] - TEAM K0242 Disclaimer: =========== 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.vulnerability-lab.com/register Contact: admin@xxxxxxxxxxxxxxxxxxxxx - support@xxxxxxxxxxxxxxxxxxxxx - research@xxxxxxxxxxxxxxxxxxxxx Section: video.vulnerability-lab.com - forum.vulnerability-lab.com - news.vulnerability-lab.com 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 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, sourcecode, 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@xxxxxxxxxxxxxxxxxxxxx or support@xxxxxxxxxxxxxxxxxxxxx) to get a permission. Copyright © 2012 | Vulnerability Laboratory -- VULNERABILITY RESEARCH LABORATORY LABORATORY RESEARCH TEAM CONTACT: research@xxxxxxxxxxxxxxxxxxxxx
