Monstra CMS 3.0.4 users.plugin.php Cookie input validation
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 8.5 | $0-$5k | 0.00 |
Summary
A vulnerability classified as problematic has been found in Monstra CMS 3.0.4. This vulnerability affects unknown code of the file plugins/box/users/users.plugin.php. This manipulation as part of Cookie causes input validation. This vulnerability is tracked as CVE-2018-11678. The attack is possible to be carried out remotely. No exploit exists.
Details
A vulnerability has been found in Monstra CMS 3.0.4 (Content Management System) and classified as critical. Affected by this vulnerability is some unknown processing of the file plugins/box/users/users.plugin.php. The manipulation as part of a Cookie leads to a input validation vulnerability. The CWE definition for the vulnerability is CWE-20. The product receives input or data, but it does
not validate or incorrectly validates that the input has the
properties that are required to process the data safely and
correctly. As an impact it is known to affect confidentiality, integrity, and availability. The summary by CVE is:
plugins/box/users/users.plugin.php in Monstra CMS 3.0.4 allows Login Rate Limiting Bypass via manipulation of the login_attempts cookie.
The bug was discovered 04/01/2018. The weakness was disclosed 06/05/2018 (Website). The advisory is shared at abdilahrf.github.io. This vulnerability is known as CVE-2018-11678 since 06/02/2018. The exploitation appears to be easy. The attack can be launched remotely. The exploitation doesn't need any form of authentication. Technical details are known, but no exploit is available.
The vulnerability was handled as a non-public zero-day exploit for at least 65 days. During that time the estimated underground price was around $0-$5k. By approaching the search of inurl:plugins/box/users/users.plugin.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.
The entry VDB-118958 is pretty similar. If you want to get the best quality for vulnerability data then you always have to consider VulDB.
Product
Type
Vendor
Name
Version
License
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 8.5VulDB Meta Temp Score: 8.5
VulDB Base Score: 7.3
VulDB Temp Score: 7.3
VulDB Vector: 🔍
VulDB Reliability: 🔍
NVD Base Score: 9.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: Input validationCWE: CWE-20
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
04/01/2018 🔍06/02/2018 🔍
06/05/2018 🔍
06/05/2018 🔍
06/05/2018 🔍
02/15/2020 🔍
Sources
Advisory: abdilahrf.github.ioStatus: Not defined
CVE: CVE-2018-11678 (🔍)
GCVE (CVE): GCVE-0-2018-11678
GCVE (VulDB): GCVE-100-118957
See also: 🔍
Entry
Created: 06/05/2018 22:04Updated: 02/15/2020 08:46
Changes: 06/05/2018 22:04 (63), 02/15/2020 08:46 (1)
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.