WordPress Multiple Meta Box 1.0 SQL Injection

Type packetstorm
Reporter Dr.Malware
Modified 2016-04-08T00:00:00


Document Title:  
WP Multiple Meta Box v1.0 - SQL Injection Vulnerability  
References (Source):  
Release Date:  
Vulnerability Laboratory ID (VL-ID):  
Common Vulnerability Scoring System:  
Product & Service Introduction:  
Multi Meta Box Plugin will help you to show Wp Multiple Meta Box on  
Front-end by Following way. Create Multi Meta Box from Admin Panel of  
Add New  
Wp Multiple Meta Box Section. Create New Multi Meta Box by Adding Meta  
Box Label, Meta Field Post Type(Posts, Pages, etc), Status (Available, Un  
Available), Click on add meta field and fill box field (Field Type (Text  
Box, Text Area, Drop Down, Check Box, Radio Button), according to your  
selected Field Type, Fill option Below Like Meta Field Type for  
(Textbox), Meta Field Title, Meta Field Value for (check Box, Radio  
Button, Drop  
Down), Meta Field Required, Meta Field Place Holder for (Textbox, Text  
Area), Meta Field Min Length for (Textbox), Meta Field Max Length for  
(Textbox) You can add Multi Metabox as many as required by clicking on  
Add Meta Field. Admins will get that Multi Meta Box on (Post, Page, etc)  
as per selection of Meta Field Post Type.  
(Copy of the Homepage: https://wordpress.org/plugins/multi-meta-box/ )  
Abstract Advisory Information:  
An independent vulnerability laboratory researcher discovered a remote  
sql-injection vulnerability in the official Wordpress Multiple Meta Box  
v1.0 plugin.  
Vulnerability Disclosure Timeline:  
2016-04-08: Public Disclosure (Vulnerability Laboratory)  
Discovery Status:  
Affected Product(s):  
Agileinfoways Ltd  
Product: Multiple Meta Box - Wordpress Plugin (Web-Application) 1.0  
Exploitation Technique:  
Severity Level:  
Technical Details & Description:  
A remote sql-injection web vulnerability has been discovered in the  
official Wordpress Multiple Meta Box v1.0 plugin web-application.  
The vulnerability allows remote attackers and privileged user accounts  
to execute own sql commands to compromise the web-server or dbms.  
The vulnerability is located in the `id` value of the  
`multi_metabox_listing` action GET method request. The vulnerability is  
on the server-side of the service and the request method to  
execute/inject is GET. The vulnerability is only with a privileged  
user account exploitable. The vulnerable module requires at minimum 1  
item for successful exploitation.  
The security risk of the sql-injection vulnerability is estimated as  
medium with a cvss (common vulnerability scoring system) count of 5.9.  
Exploitation of the remote sql injection web vulnerability requires no  
user interaction and a low 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 Function(s):  
[+] multi_metabox_listing  
Vulnerable Parameter(s):  
[+] id  
Proof of Concept (PoC):  
The remote sql-injection web vulnerability can be exploited by  
privileged web-application user account without user interaction.  
For security demonstration or to reproduce the vulnerability follow the  
provided information and steps below to continue.  
Solution - Fix & Patch:  
The vulnerability can be patched by usage of a prepared statement with  
clear set entities in the id value of the page GET method request.  
Encode the input values of the parameter and restrict the input by usage  
of special chars. Escape the entries to prevent the vulnerability.  
Security Risk:  
The security risk of the remote sql-injection web vulnerability in the  
wordpress multiple meta box plugin is estimated as medium. (CVSS 5.9)  
Credits & Authors:  
Dr.Malware - [http://www.vulnerability-lab.com/show.php?user=Dr%20Malware]  
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 licenses, policies, deface websites, hack into databases or  
trade with stolen data.  
Domains: www.vulnerability-lab.com - www.vuln-lab.com   
- www.evolution-sec.com  
Contact: admin@vulnerability-lab.com -  
research@vulnerability-lab.com - admin@evolution-sec.com  
Section: magazine.vulnerability-lab.com -  
vulnerability-lab.com/contact.php -  
Social: twitter.com/vuln_lab -  
facebook.com/VulnerabilityLab -  
Feeds: vulnerability-lab.com/rss/rss.php -  
vulnerability-lab.com/rss/rss_upcoming.php -  
Programs: vulnerability-lab.com/submit.php -  
vulnerability-lab.com/list-of-bug-bounty-programs.php -  
Any modified copy or reproduction, including partially usages, of this  
file requires authorization from Vulnerability Laboratory. Permission to  
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@ or research@vulnerability-lab.com) to get a ask permission.  
Copyright © 2016 | Vulnerability Laboratory -  
[Evolution Security GmbH]™  
SERVICE: www.vulnerability-lab.com  
CONTACT: research@vulnerability-lab.com