Back to list
Zenario v7.6 CMS - SQL Injection Web Vulnerability
Jan 15 2018 11:02PM
Vulnerability Lab (research vulnerability-lab com)
Zenario v7.6 CMS - SQL Injection Web Vulnerability
Vulnerability Laboratory ID (VL-ID):
Common Vulnerability Scoring System:
Current Estimated Price:
500â?¬ - 1.000â?¬
Product & Service Introduction:
Zenario is a web-based content management system for sites with one or many languages. It's designed to grow with
your site, adding extranet, online database and custom functionality when you need it. Zenario 7.2 has a new feature
to add CSS styles and media queries, thereby allowing you to make mobile-friendly "responsive" email newsletters.
(Copy of the Homepage: http://zenar.io/ )
Abstract Advisory Information:
The vulnerability laboratory core research team discovered a remote sql-injection vulnerability in the official Zenario v7.6 content management system.
Vulnerability Disclosure Timeline:
2018-01-16: Public Disclosure (Vulnerability Laboratory)
Product: Zenario - Content Management System (Web-Application) 7.1
Product: Zenario - Content Management System (Web-Application) 7.2
Product: Zenario - Content Management System (Web-Application) 7.3
Product: Zenario - Content Management System (Web-Application) 7.4
Product: Zenario - Content Management System (Web-Application) 7.5
Product: Zenario - Content Management System (Web-Application) 7.6
Technical Details & Description:
A remote sql-injection web vulnerability has been discovered in the official Zenario v7.1 - v7.6 content management system web-application.
The sql-injection web vulnerability allows remote attackers with restricted account to execute own malicious sql commands to compromise
the web-application and database management system.
The sql-injection vulnerability is location in the `Name` input field of the `Categories - Edit` module create POST method request.
Remote attackers with restricted privileged accounts are able to execute own malicious sql commands to compromise the application.
The attack vector of the vulnerability occurs on the client-side and the request method to inject is POST.
The security risk of the sql-injection vulnerability is estimated as medium with a common vulnerability scoring system count of 5.7.
Exploitation of the sql-injection web vulnerability requires a restricted site admin user account without user interaction.
Successful exploitation of the sql-injection vulnerability results in web-application or database management system compromise.
[+] Categories - Edit
[+] Name (current_value)
Proof of Concept (PoC):
The sql-injection vulnerability can be exploited by remote attackers with restricted user account without user interaction.
For security demonstration or to reproduce the vulnerability follow the provided information and steps below to continue.
Vulnerable Module: Categories > Edit > Name - Current_Value (Input Field)
--- PoC Session Logs [GET] (restricted_admin) ---
User-Agent[Mozilla/5.0 (Windows NT 10.0; WOW64; rv:51.0) Gecko/20100101 Firefox/51.0]
Cookie[__cfduid=; PHPSESSID=; COOKIE_LAST_ADMIN_USER=restricted_admin; cookies_accepted=1]
Solution - Fix & Patch:
1. Escape the content of the name input field
2. Sanitize the parameter of the current_value
3. Disallow the usage of special chars in the current_value parameter
4. Use a prepared statement to prevent further exploitation
The security risk of the remote sql-injection web vulnerability in the web-application is estimated as medium (cvss 5.7).
Credits & Authors:
Vulnerability-Lab [research (at) vulnerability-lab (dot) com [email concealed]] - https://www.vulnerability-lab.com/show.php?user=Vulnerability-Lab
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 Labs or its
suppliers have been advised of the possibility of such damages. Some states do not allow the exclusion or limitation of liability mainly for incidental
or consequential 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. We have no need for criminal activities or membership requests. We do not publish advisories
or vulnerabilities of religious-, militant- and racist- hacker/analyst/researcher groups or individuals. We do not publish trade researcher mails,
phone numbers, conversations or anything else to journalists, investigative authorities or private individuals.
Domains: www.vulnerability-lab.com - www.vulnerability-db.com - www.evolution-sec.com
Programs: vulnerability-lab.com/submit.php - vulnerability-lab.com/list-of-bug-bounty-programs.php - vulnerability-lab.com/register.php
Feeds: vulnerability-lab.com/rss/rss.php - vulnerability-lab.com/rss/rss_upcoming.php - vulnerability-lab.com/rss/rss_news.php
Social: twitter.com/vuln_lab - facebook.com/VulnerabilityLab - youtube.com/user/vulnerability0lab
Any modified copy or reproduction, including partially usages, of this file, resources or information 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@) to get an ask permission.
Copyright Â© 2018 | Vulnerability Laboratory - [Evolution Security GmbH]â?¢
VULNERABILITY LABORATORY - RESEARCH TEAM
[ reply ]
Copyright 2010, SecurityFocus