DBHcms 1.2.0 mod.editor.php $_GET['file'] information disclosure
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 3.8 | $0-$5k | 0.00 |
Summary
A vulnerability classified as problematic was found in DBHcms 1.2.0. This impacts an unknown function of the file dbhcms\mod\mod.editor.php. Such manipulation of the argument $_GET['file'] as part of Filename leads to information disclosure. This vulnerability is uniquely identified as CVE-2020-19890. The attack can be launched remotely. No exploit exists.
Details
A vulnerability, which was classified as problematic, has been found in DBHcms 1.2.0. Affected by this issue is an unknown function of the file dbhcms\mod\mod.editor.php. The manipulation of the argument $_GET['file'] as part of a Filename leads to a information disclosure vulnerability. Using CWE to declare the problem leads to CWE-200. The product exposes sensitive information to an actor that is not explicitly authorized to have access to that information. Impacted is confidentiality. CVE summarizes:
DBHcms v1.2.0 has an Arbitrary file read vulnerability in dbhcms\mod\mod.editor.php $_GET['file'] is filename,and as there is no filter function for security, you can read any file's content.
The weakness was disclosed 08/24/2020. This vulnerability is handled as CVE-2020-19890 since 08/13/2020. The exploitation is known to be easy. The attack may be launched remotely. The successful exploitation requires a simple authentication. Technical details are known, but there is no available exploit. This vulnerability is assigned to T1592 by the MITRE ATT&CK project.
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.
The entries VDB-160203, VDB-160201, VDB-160200 and VDB-160199 are pretty similar. If you want to get best quality of vulnerability data, you may have to visit VulDB.
Product
Name
Version
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 3.8VulDB Meta Temp Score: 3.8
VulDB Base Score: 2.7
VulDB Temp Score: 2.7
VulDB Vector: 🔍
VulDB Reliability: 🔍
NVD Base Score: 4.9
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: Information disclosureCWE: CWE-200 / CWE-284 / CWE-266
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-19890 (🔍)
GCVE (CVE): GCVE-0-2020-19890
GCVE (VulDB): GCVE-100-160202
See also: 🔍
Entry
Created: 08/24/2020 20:16Updated: 08/24/2020 20:21
Changes: 08/24/2020 20:16 (37), 08/24/2020 20:21 (17)
Complete: 🔍
Cache ID: 216::103
If you want to get best quality of vulnerability data, you may have to visit VulDB.
No comments yet. Languages: en.
Please log in to comment.