YXcms 1.4.7 photoController.php picname access control
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 4.3 | $0-$5k | 0.00 |
Summary
A vulnerability identified as problematic has been detected in YXcms 1.4.7. The affected element is an unknown function of the file protected/apps/admin/controller/photoController.php. This manipulation of the argument picname as part of Parameter causes access control. This vulnerability is registered as CVE-2018-13025. Remote exploitation of the attack is possible. No exploit is available.
Details
A vulnerability classified as problematic was found in YXcms 1.4.7. Affected by this vulnerability is some unknown functionality of the file protected/apps/admin/controller/photoController.php. The manipulation of the argument picname as part of a Parameter leads to a access control vulnerability. The CWE definition for the vulnerability is CWE-284. The product does not restrict or incorrectly restricts access to a resource from an unauthorized actor. As an impact it is known to affect integrity, and availability. The summary by CVE is:
protected/apps/admin/controller/photoController.php in YXcms 1.4.7 allows remote attackers to delete arbitrary files via the index.php?r=admin/photo/delpic picname parameter.
The bug was discovered 06/29/2018. The weakness was published 06/29/2018 (Website). It is possible to read the advisory at github.com. This vulnerability is known as CVE-2018-13025 since 06/29/2018. The exploitation appears to be easy. The attack can be launched remotely. A single authentication is required for exploitation. Technical details of the vulnerability are known, but there is no available exploit. The attack technique deployed by this issue is T1068 according to MITRE ATT&CK.
By approaching the search of inurl:protected/apps/admin/controller/photoController.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
Name
Version
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 4.3VulDB Meta Temp Score: 4.3
VulDB Base Score: 3.8
VulDB Temp Score: 3.8
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: Access controlCWE: 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: 🔍
Timeline
06/29/2018 🔍06/29/2018 🔍
06/29/2018 🔍
06/29/2018 🔍
06/30/2018 🔍
02/23/2020 🔍
Sources
Advisory: github.comStatus: Not defined
CVE: CVE-2018-13025 (🔍)
GCVE (CVE): GCVE-0-2018-13025
GCVE (VulDB): GCVE-100-120115
Entry
Created: 06/30/2018 08:34Updated: 02/23/2020 13:45
Changes: 06/30/2018 08:34 (56), 02/23/2020 13:45 (1)
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.