DBHcms 1.2.0 TinyMCE mod.editor.php $_POST['updatefile']/$_POST['tinymce_content'] out-of-bounds write
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 6.7 | $0-$5k | 0.00 |
Summary
A vulnerability, which was classified as critical, has been found in DBHcms 1.2.0. Affected is an unknown function of the file dbhcms\mod\mod.editor.php of the component TinyMCE. Performing a manipulation of the argument $_POST['updatefile']/$_POST['tinymce_content'] results in out-of-bounds write. This vulnerability was named CVE-2020-19891. The attack may be initiated remotely. There is no available exploit.
Details
A vulnerability, which was classified as critical, was found in DBHcms 1.2.0. This affects an unknown functionality of the file dbhcms\mod\mod.editor.php of the component TinyMCE. The manipulation of the argument $_POST['updatefile']/$_POST['tinymce_content'] with an unknown input leads to a out-of-bounds write vulnerability. CWE is classifying the issue as CWE-787. The product writes data past the end, or before the beginning, of the intended buffer. This is going to have an impact on confidentiality, integrity, and availability. The summary by CVE is:
DBHcms v1.2.0 has an Arbitrary file write vulnerability in dbhcms\mod\mod.editor.php $_POST['updatefile'] is filename and $_POST['tinymce_content'] is file content, there is no filter function for security. A remote authenticated admin user can exploit this vulnerability to get a webshell.
The weakness was presented 08/24/2020. This vulnerability is uniquely identified as CVE-2020-19891 since 08/13/2020. It is possible to initiate the attack remotely. The successful exploitation needs a authentication. Technical details of the vulnerability are known, but there is no available exploit.
By approaching the search of inurl:dbhcms\mod\mod.editor.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.
See VDB-160202, VDB-160201, VDB-160200 and VDB-160199 for similar entries. Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.
Product
Name
Version
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 6.7VulDB Meta Temp Score: 6.7
VulDB Base Score: 6.3
VulDB Temp Score: 6.3
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: Out-of-bounds writeCWE: CWE-787 / CWE-119
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
08/13/2020 🔍08/24/2020 🔍
08/24/2020 🔍
08/24/2020 🔍
Sources
Status: Not definedCVE: CVE-2020-19891 (🔍)
GCVE (CVE): GCVE-0-2020-19891
GCVE (VulDB): GCVE-100-160203
See also: 🔍
Entry
Created: 08/24/2020 20:17Updated: 08/24/2020 20:22
Changes: 08/24/2020 20:17 (37), 08/24/2020 20:22 (17)
Complete: 🔍
Cache ID: 216::103
Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.
No comments yet. Languages: en.
Please log in to comment.