Share
Document Title:
===============
Discuz!ML v3.x - Code Injection Vulnerability


References:
===========
https://www.vulnerability-lab.com/get_content.php?id=2185

Download: https://www.vulnerability-lab.com/resources/documents/2185.rar



Release Date:
=============
2019-07-08


Vulnerability Laboratory ID (VL-ID):
====================================
2185


Common Vulnerability Scoring System:
====================================
6.4


Vulnerability Class:
====================
Command Injection


Vulnerability Disclosure Timeline:
==================================
2019-07-08: Public Disclosure (Vulnerability Laboratory)


Discovery Status:
=================
Published


Exploitation Technique:
=======================
Tutorial


Severity Level:
===============
Medium


Authentication Type:
====================
Pre auth - no privileges


User Interaction:
=================
No User Interaction


Disclosure Type:
================
Independent Security Research


Technical Details & Description:
================================
The document explains a simple code injection vulnerability in the discuz!ml content management system writting in php using mysql.
The vulnerability can be exploited by remote attackers without user interaction or privileged application user account.
The request method to inject is get and the vulnerability is located on the application-side of the online service.
Feel free to read the short small tutorial about how to exploit a code injection issue for discuz!ml.


Credits & Authors:
==================
Vulnerability-Lab [admin@vulnerability-lab.com] - 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-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.vulnerability-db.com
Services:   magazine.vulnerability-lab.com	paste.vulnerability-db.com 			infosec.vulnerability-db.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
Programs:   vulnerability-lab.com/submit.php 	vulnerability-lab.com/register.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 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@ or research@) to get a ask permission.

				    Copyright ยฉ 2019 | Vulnerability Laboratory - [Evolution Security GmbH]โ„ข