PopojiCMS 2.0.1 route.php?mod=component&act=addnew cross-site request forgery
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 6.5 | $0-$5k | 0.00 |
Summary
A vulnerability, which was classified as problematic, has been found in PopojiCMS 2.0.1. This issue affects some unknown processing of the file po-admin/route.php?mod=component&act=addnew. The manipulation leads to cross-site request forgery. This vulnerability is traded as CVE-2018-18935. It is possible to initiate the attack remotely. There is no exploit available.
Details
A vulnerability was found in PopojiCMS 2.0.1 (Content Management System). It has been rated as problematic. This issue affects an unknown functionality of the file po-admin/route.php?mod=component&act=addnew. The manipulation with an unknown input leads to a cross-site request forgery vulnerability. Using CWE to declare the problem leads to CWE-352. The web application does not, or can not, sufficiently verify whether a well-formed, valid, consistent request was intentionally provided by the user who submitted the request. Impacted is integrity. The summary by CVE is:
An issue was discovered in PopojiCMS v2.0.1. It has CSRF via the po-admin/route.php?mod=component&act=addnew URI, as demonstrated by adding a level=1 account.
The bug was discovered 10/30/2018. The weakness was shared 11/05/2018 (Website). The advisory is shared at github.com. The identification of this vulnerability is CVE-2018-18935 since 11/05/2018. The attack may be initiated remotely. No form of authentication is needed for a successful exploitation. It demands that the victim is doing some kind of user interaction. Technical details are known, but no exploit is available.
The vulnerability was handled as a non-public zero-day exploit for at least 6 days. During that time the estimated underground price was around $0-$5k.
There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.
The entries VDB-126448 and VDB-126450 are related to this item. Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
Product
Type
Name
Version
Website
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 6.6VulDB Meta Temp Score: 6.6
VulDB Base Score: 4.3
VulDB Temp Score: 4.3
VulDB Vector: 🔍
VulDB Reliability: 🔍
NVD Base Score: 8.8
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: Cross-site request forgeryCWE: CWE-352 / CWE-862 / CWE-863
CAPEC: 🔍
ATT&CK: 🔍
Physical: No
Local: No
Remote: Yes
Availability: 🔍
Status: Not defined
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
10/30/2018 🔍11/05/2018 🔍
11/05/2018 🔍
11/05/2018 🔍
11/05/2018 🔍
06/04/2023 🔍
Sources
Product: github.comAdvisory: 14
Status: Not defined
CVE: CVE-2018-18935 (🔍)
GCVE (CVE): GCVE-0-2018-18935
GCVE (VulDB): GCVE-100-126449
See also: 🔍
Entry
Created: 11/05/2018 15:49Updated: 06/04/2023 14:39
Changes: 11/05/2018 15:49 (57), 04/10/2020 08:50 (1), 06/04/2023 14:39 (3)
Complete: 🔍
Cache ID: 216::103
Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
No comments yet. Languages: en.
Please log in to comment.