DedeCMS 5.7.118 file_manage_control.php privilege escalation
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 6.1 | $0-$5k | 0.64- |
Summary
A vulnerability was found in DedeCMS 5.7.118. It has been classified as critical. Affected by this vulnerability is an unknown functionality of the file file_manage_control.php. This manipulation causes Remote Privilege Escalation. This vulnerability is tracked as CVE-2026-38615. The attack is possible to be carried out remotely. No exploit exists.
Details
A vulnerability has been found in DedeCMS 5.7.118 and classified as critical. Affected by this vulnerability is an unknown code block of the file file_manage_control.php. The manipulation with an unknown input leads to a remote privilege escalation vulnerability. As an impact it is known to affect confidentiality, integrity, and availability. The summary by CVE is:
DedeCMS V5.7.118 is vulnerable to Command Execution in file_manage_control.php.
It is possible to read the advisory at github.com. This vulnerability is known as CVE-2026-38615 since 04/06/2026. The exploitation appears to be easy. The attack can be launched remotely. Technical details of the vulnerability are known, but there is no available exploit. The pricing for an exploit might be around USD $0-$5k at the moment (estimation calculated on 06/09/2026).
By approaching the search of inurl:file_manage_control.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.
Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.
Product
Type
Name
Version
License
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔒VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 6.3VulDB Meta Temp Score: 6.1
VulDB Base Score: 6.3
VulDB Temp Score: 6.1
VulDB Vector: 🔒
VulDB Reliability: 🔍
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: Privilege escalationCWE: Unknown
CAPEC: 🔒
ATT&CK: 🔒
Physical: No
Local: No
Remote: Yes
Availability: 🔒
Status: Not defined
Google Hack: 🔒
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
04/06/2026 CVE reserved06/09/2026 Advisory disclosed
06/09/2026 VulDB entry created
06/09/2026 VulDB entry last update
Sources
Advisory: github.comStatus: Not defined
CVE: CVE-2026-38615 (🔒)
GCVE (CVE): GCVE-0-2026-38615
GCVE (VulDB): GCVE-100-369787
Entry
Created: 06/09/2026 20:58Changes: 06/09/2026 20:58 (51)
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.