Qihang QiHang Media Web Digital Signage 3.0.9.0 QH.aspx path/filename backup
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 5.7 | $0-$5k | 0.00 |
Summary
A vulnerability was found in Qihang QiHang Media Web Digital Signage 3.0.9.0. It has been declared as problematic. This affects an unknown part of the file QH.aspx. Such manipulation of the argument path/filename leads to backup. This vulnerability is referenced as CVE-2020-36899. It is possible to launch the attack remotely. Furthermore, an exploit is available.
Details
A vulnerability, which was classified as problematic, has been found in Qihang QiHang Media Web Digital Signage 3.0.9.0. Affected by this issue is some unknown processing of the file QH.aspx. The manipulation of the argument path/filename with an unknown input leads to a backup vulnerability. Using CWE to declare the problem leads to CWE-530. A backup file is stored in a directory or archive that is made accessible to unauthorized actors. Impacted is confidentiality. CVE summarizes:
QiHang Media Web Digital Signage 3.0.9 contains an unauthenticated file disclosure vulnerability that allows remote attackers to access sensitive files through unverified 'filename' and 'path' parameters. Attackers can exploit the QH.aspx endpoint to read arbitrary files and directory contents without authentication by manipulating download and getAll actions.
The weakness was published by Gjoko Krstic as 48750. The advisory is available at exploit-db.com. This vulnerability is handled as CVE-2020-36899 since 12/09/2025. The exploitation is known to be easy. The attack may be launched remotely. No form of authentication is required for exploitation. Successful exploitation requires user interaction by the victim. Technical details as well as a public exploit are known.
The exploit is available at exploit-db.com. It is declared as proof-of-concept. By approaching the search of inurl:QH.aspx 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 vulnerability is also documented in the vulnerability database at Exploit-DB (48750). If you want to get best quality of vulnerability data, you may have to visit VulDB.
Product
Vendor
Name
Version
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔒VulDB Reliability: 🔍
CNA CVSS-B Score: 🔒
CNA CVSS-BT Score: 🔒
CNA Vector: 🔒
CVSSv3
VulDB Meta Base Score: 5.9VulDB Meta Temp Score: 5.7
VulDB Base Score: 4.3
VulDB Temp Score: 3.9
VulDB Vector: 🔒
VulDB Reliability: 🔍
NVD Base Score: 7.5
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: 🔍
Exploiting
Class: BackupCWE: CWE-530 / CWE-285 / CWE-266
CAPEC: 🔒
ATT&CK: 🔒
Physical: No
Local: No
Remote: Yes
Availability: 🔒
Access: Public
Status: Proof-of-Concept
Download: 🔒
Google Hack: 🔒
EPSS Score: 🔒
EPSS Percentile: 🔒
Price Prediction: 🔍
Current Price Estimation: 🔒
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Exploit-DB: 🔒
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: no mitigation knownStatus: 🔍
0-Day Time: 🔒
Timeline
12/09/2025 CVE reserved12/11/2025 Advisory disclosed
12/11/2025 VulDB entry created
12/18/2025 VulDB entry last update
Sources
Advisory: 48750Researcher: Gjoko Krstic
Status: Not defined
CVE: CVE-2020-36899 (🔒)
GCVE (CVE): GCVE-0-2020-36899
GCVE (VulDB): GCVE-100-335810
scip Labs: https://www.scip.ch/en/?labs.20161013
Entry
Created: 12/11/2025 07:28Updated: 12/18/2025 14:51
Changes: 12/11/2025 07:28 (71), 12/18/2025 14:51 (11)
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.