doorGets 7.0 modulecategoryRequest.php modulecategory_add_titre sql injection
|CVSS Meta Temp Score|
CVSS is a standardized scoring system to determine possibilities of attacks. The Temp Score considers temporal factors like disclosure, exploit and countermeasures. The unique Meta Score calculates the average score of different sources to provide a normalized scoring system.
|Current Exploit Price (≈)|
Our analysts are monitoring exploit markets and are in contact with vulnerability brokers. The range indicates the observed or calculated exploit price to be seen on exploit markets. A good indicator to understand the monetary effort required for and the popularity of an attack.
|CTI Interest Score|
Our Cyber Threat Intelligence team is monitoring different web sites, mailing lists, exploit markets and social media networks. The CTI Interest Score identifies the interest of attackers and the security community for this specific vulnerability in real-time. A high score indicates an elevated risk to be targeted for this vulnerability.
A vulnerability classified as critical was found in doorGets 7.0. Affected by this vulnerability is an unknown part of the file /doorgets/app/requests/user/modulecategoryRequest.php. The manipulation of the argument
modulecategory_add_titre with an unknown input leads to a sql injection vulnerability. The CWE definition for the vulnerability is CWE-89. As an impact it is known to affect confidentiality, integrity, and availability. An attacker might be able inject and/or alter existing SQL statements which would influence the database exchange. The summary by CVE is:
doorGets 7.0 has a SQL injection vulnerability in /doorgets/app/requests/user/modulecategoryRequest.php. A remote background administrator privilege user (or a user with permission to manage modulecategory) could exploit the vulnerability to obtain database sensitive information via modulecategory_add_titre.
The bug was discovered 04/24/2019. The weakness was presented 04/30/2019. This vulnerability is known as CVE-2019-11620 since 04/30/2019. The attack can be launched remotely. A single authentication is necessary for exploitation. Technical details of the vulnerability are known, but there is no available exploit.
The vulnerability was handled as a non-public zero-day exploit for at least 6 days. During that time the estimated underground price was around $0-$5k.
There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.
CVSSv3VulDB Meta Base Score: 4.8
VulDB Meta Temp Score: 4.8
VulDB Base Score: 4.7
VulDB Temp Score: 4.7
VulDB Vector: 🔍
VulDB Reliability: 🔍
NVD Base Score: 4.9
NVD Vector: 🔍
VulDB Base Score: 🔍
VulDB Temp Score: 🔍
VulDB Reliability: 🔍
NVD Base Score: 🔍
ExploitingClass: Sql injection
Status: Not defined
Price Prediction: 🔍
Current Price Estimation: 🔍
Threat IntelligenceThreat: 🔍
CountermeasuresRecommended: no mitigation known
0-Day Time: 🔍
04/30/2019 +6 days 🔍
04/30/2019 +0 days 🔍
05/01/2019 +1 days 🔍
06/05/2020 +401 days 🔍
SourcesStatus: Not defined
CVE: CVE-2019-11620 (🔍)
See also: 🔍
EntryCreated: 05/01/2019 01:57 PM
Updated: 06/05/2020 09:55 AM
Changes: (1) vulnerability_discoverydate
Do you want to use VulDB in your project?
Use the official API to access entries easily!