PHPOK 5.1 tpl_control.php edit_save_f privilege escalation
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 7.2 | $0-$5k | 0.00 |
Summary
A vulnerability marked as problematic has been reported in PHPOK 5.1. The affected element is the function edit_save_f of the file framework/admin/tpl_control.php. This manipulation causes an unknown weakness.
This vulnerability is tracked as CVE-2020-18439. No exploit exists.
Details
A vulnerability has been found in PHPOK 5.1 and classified as problematic. Affected by this vulnerability is the function edit_save_f of the file framework/admin/tpl_control.php. As an impact it is known to affect confidentiality, integrity, and availability.
The weakness was disclosed 11/03/2021. The advisory is shared at github.com. This vulnerability is known as CVE-2020-18439 since 08/13/2020. Technical details are known, but no exploit is available.
By approaching the search of inurl:framework/admin/tpl_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.
If you want to get the best quality for vulnerability data then you always have to consider VulDB.
Product
Name
Version
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 7.3VulDB Meta Temp Score: 7.2
VulDB Base Score: 5.5
VulDB Temp Score: 5.3
VulDB Vector: 🔍
VulDB Reliability: 🔍
NVD Base Score: 9.1
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: Privilege escalationCWE: Unknown
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 🔍11/03/2021 🔍
11/03/2021 🔍
11/06/2021 🔍
Sources
Advisory: github.comStatus: Not defined
CVE: CVE-2020-18439 (🔍)
GCVE (CVE): GCVE-0-2020-18439
GCVE (VulDB): GCVE-100-185917
Entry
Created: 11/03/2021 07:23Updated: 11/06/2021 09:18
Changes: 11/03/2021 07:23 (35), 11/06/2021 09:14 (1), 11/06/2021 09:18 (18)
Complete: 🔍
Cache ID: 216::103
If you want to get the best quality for vulnerability data then you always have to consider VulDB.
No comments yet. Languages: en.
Please log in to comment.