VamCart v0.9 CMS - Multiple Web Vulnerabilities

2012-07-23T00:00:00
ID SECURITYVULNS:DOC:28327
Type securityvulns
Reporter Securityvulns
Modified 2012-07-23T00:00:00

Description

Title:

VamCart v0.9 CMS - Multiple Web Vulnerabilities

Date:

2012-06-25

References:

http://www.vulnerability-lab.com/get_content.php?id=622

VL-ID:

622

Common Vulnerability Scoring System:

4

Introduction:

VamCart is a Free, Open Source, CakePHP Based Shopping Cart Content Management System. VamCart is a Open Source Project under the GNU GPL license with the following features ...

Easy Installation.
SEO - Search Engine Optimization.
Unlimited Categories, Products.
CakePHP, MVC, Smarty.
Multi Language, Multi Currency.
Templatable.
Open Source.
Automatic Image Resize.
Product Reviews.
Coupons ...

(Copy of the Vendor Homepage: http://vamcart.com )

Abstract:

The Vulnerability Laboratory Research Team discovered multiple Web Vulnerabilities in the VamCart v0.9 Content Management System.

Report-Timeline:

2012-06-25: Public or Non-Public Disclosure

Status:

Published

Exploitation-Technique:

Remote

Severity:

Medium

Details:

Multiple persistent input validation vulnerabilities are detected in the VamCart v0.9 Content Management System. The bugs allow remote attackers to implement/inject malicious script code on the application side (persistent). The persistent vulnerabilities are located in the manage accounts, manage coupons, view orders or order comments module(s) with the bound vulnerable parameters comment text, coupon code, title & name. Exploitation requires low user inter action & privileged application user account. Successful exploitation of the vulnerability can lead to session hijacking (admin) or stable (persistent) context manipulation.

Vulnerable Module(s): [+] Account > Manage Accounts > Admins Listing [+] Manage Coupons & Listing [+] View All Orders Listing [+] Order Comments Listing

Vulnerable Module(s): [+] Title [+] Name [+] Coupon Code [+] Comments Text

Proof of Concept:

The persistent input validation vulnerabilities can be exploited by low privileged user accounts with low required user inter action. For demonstration or reproduce ...

Review: Users [View All] INDEX - Account Listing

<tbody><tr><th>Title</th> <th>Action</th></tr><tr class="contentRowEven" onmouseout="this.className='contentRowEven';" onmouseover="this.className='contentRowEvenHover';"><td>admin</td> <td align="center"><a href="http://127.0.0.1:1338/cmspath/users/ admin_delete/1" onclick="return confirm('Confirm delete action?');"><img src="Admins%20Listing-Dateien/delete.png" alt="Delete"> </a></td></tr><tr class="contentRowOddHover" onmouseout="this.className='contentRowOdd';" onmouseover="this.className=' contentRowOddHover';"><td>"><iframe src="Admins%20Listing-Dateien/[PERSISTENT SCRIPT CODE] <<="" td=""> <td align="center"><a href="127.0.0.1:1338/cmspath/users/admin_delete/2"

URL: http://127.0.0.1:1338/[PATH CMS]/users/admin/

Review: Orders [View All] INDEX via Add - Orders Listing

<tr class="contentRowEven" onmouseout="this.className='contentRowEven';" onmouseover="this.className='contentRowEvenHover';"> <td>9 minutes ago</td> <td><img src="view-allorders.1-Dateien/true.png" alt="True"></td> <td>"><iframe src=" view-allorders.1-Dateien/[PERSISTENT SCRIPT CODE] <' <"=""><[PERSISTENT SCRIPT CODE] <") <"><[PERSISTENT SCRIPT CODE] < ) <"><[PERSISTENT SCRIPT CODE] < <"><[PERSISTENT SCRIPT CODE] < <"><iframe src=a onload=alert("VL") <</td></tr></table></div><div

URL: http://127.0.0.1:1338/[PATH CMS]/orders/admin/

Review: Manage Coupons - Coupon Code Listing

<tbody><tr><th>Name</th> <th>Code</th> <th>Action</th></tr><tr class="contentRowEven" onmouseout="this.className=' contentRowEven';" onmouseover="this.className='contentRowEvenHover';"><td><a href="http://127.0.0.1:1338/module_coupons/admin/ admin_edit/1">"><no ^^ <</a></td> <td> "><[PERSISTENT SCRIPT CODE])' <<="" td=""> <td><a

URL: http://127.0.0.1:1338/[PATH CMS]/module_coupons/admin/admin_index/

Risk:

The security risk of the persistent web vulnerabilities are estimated as medium.

Credits:

Vulnerability Laboratory [Research Team] - Benjamin Kunz Mejri (bkm@vulnerability-lab.com)

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.

Domains: www.vulnerability-lab.com - www.vuln-lab.com Contact: admin@vulnerability-lab.com - support@vulnerability-lab.com - research@vulnerability-lab.com 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

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@vulnerability-lab.com or support@vulnerability-lab.com) to get a permission.

                                            Copyright © 2012 Vulnerability-Lab

-- VULNERABILITY RESEARCH LABORATORY TEAM Website: www.vulnerability-lab.com Mail: research@vulnerability-lab.com