ThinkCMF X2.2.2 SlideController.class.php delete ids[] sql injection
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 5.9 | $0-$5k | 0.00 |
Summary
A vulnerability was found in ThinkCMF X2.2.2. It has been classified as critical. This vulnerability affects the function delete of the file SlideController.class.php. The manipulation of the argument ids[] as part of Parameter leads to sql injection.
This vulnerability is traded as CVE-2018-19896. It is possible to initiate the attack remotely. There is no exploit available.
Details
A vulnerability, which was classified as critical, has been found in ThinkCMF X2.2.2. This issue affects the function delete of the file SlideController.class.php. The manipulation of the argument ids[] as part of a Parameter leads to a sql injection vulnerability. Using CWE to declare the problem leads to CWE-89. The product constructs all or part of an SQL command using externally-influenced input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could modify the intended SQL command when it is sent to a downstream component. Impacted is confidentiality, integrity, and availability. The summary by CVE is:
ThinkCMF X2.2.2 has SQL Injection via the function delete() in SlideController.class.php and is exploitable with the manager privilege via the ids[] parameter in a slide action.
The bug was discovered 12/05/2018. The weakness was shared 12/06/2018 (Website). It is possible to read the advisory at github.com. The identification of this vulnerability is CVE-2018-19896 since 12/05/2018. The exploitation is known to be easy. The attack may be initiated remotely. The requirement for exploitation is a simple authentication. Technical details of the vulnerability are known, but there is no available exploit. The attack technique deployed by this issue is T1505 according to MITRE ATT&CK.
By approaching the search of inurl:SlideController.class.php it is possible to find vulnerable targets with Google Hacking.
There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.
The entries VDB-127557, VDB-127558, VDB-127560 and VDB-127561 are related to this item. Be aware that VulDB is the high quality source for vulnerability data.
Product
Name
Version
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 5.9VulDB Meta Temp Score: 5.9
VulDB Base Score: 4.7
VulDB Temp Score: 4.7
VulDB Vector: 🔍
VulDB Reliability: 🔍
NVD Base Score: 7.2
NVD Vector: 🔍
CVSSv2
| AV | AC | Au | C | I | A |
|---|---|---|---|---|---|
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| Vector | Complexity | Authentication | Confidentiality | Integrity | Availability |
|---|---|---|---|---|---|
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
VulDB Base Score: 🔍
VulDB Temp Score: 🔍
VulDB Reliability: 🔍
NVD Base Score: 🔍
Exploiting
Class: Sql injectionCWE: CWE-89 / CWE-74 / CWE-707
CAPEC: 🔍
ATT&CK: 🔍
Physical: No
Local: No
Remote: Yes
Availability: 🔍
Status: Not defined
Google Hack: 🔍
EPSS Score: 🔍
EPSS Percentile: 🔍
Price Prediction: 🔍
Current Price Estimation: 🔍
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: no mitigation knownStatus: 🔍
0-Day Time: 🔍
Timeline
12/05/2018 🔍12/05/2018 🔍
12/05/2018 🔍
12/06/2018 🔍
12/06/2018 🔍
06/13/2023 🔍
Sources
Advisory: 26Status: Not defined
CVE: CVE-2018-19896 (🔍)
GCVE (CVE): GCVE-0-2018-19896
GCVE (VulDB): GCVE-100-127559
See also: 🔍
Entry
Created: 12/06/2018 11:28Updated: 06/13/2023 12:34
Changes: 12/06/2018 11:28 (58), 04/18/2020 08:36 (1), 06/13/2023 12:34 (3)
Complete: 🔍
Cache ID: 216::103
Be aware that VulDB is the high quality source for vulnerability data.
No comments yet. Languages: en.
Please log in to comment.