MULTIDOTS WooCommerce Banner Management Plugin 1.1.0 on WordPress class-woo-banner-management.php Request improper authentication
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 6.3 | $0-$5k | 0.00 |
Summary
A vulnerability marked as critical has been reported in MULTIDOTS WooCommerce Banner Management Plugin 1.1.0 on WordPress. This affects an unknown part of the file class-woo-banner-management.php. Performing a manipulation as part of Request results in improper authentication. This vulnerability is known as CVE-2018-11579. Remote exploitation of the attack is possible. No exploit is available.
Details
A vulnerability classified as critical has been found in MULTIDOTS WooCommerce Banner Management Plugin 1.1.0 on WordPress (E-Commerce Management Software). This affects an unknown code of the file class-woo-banner-management.php. The manipulation as part of a Request leads to a improper authentication vulnerability. CWE is classifying the issue as CWE-287. When an actor claims to have a given identity, the product does not prove or insufficiently proves that the claim is correct. This is going to have an impact on confidentiality, integrity, and availability. The summary by CVE is:
class-woo-banner-management.php in the MULTIDOTS WooCommerce Category Banner Management plugin 1.1.0 for WordPress has an Unauthenticated Settings Change Vulnerability, related to certain wp_ajax_nopriv_ usage. Anyone can change the plugin's setting by simply sending a request with a wbm_save_shop_page_banner_data action.
The bug was discovered 05/30/2018. The weakness was published 05/31/2018 (Website). It is possible to read the advisory at labs.threatpress.com. This vulnerability is uniquely identified as CVE-2018-11579 since 05/30/2018. It is possible to initiate the attack remotely. No form of authentication is needed for exploitation. Technical details of the vulnerability are known, but there is no available exploit.
By approaching the search of inurl:class-woo-banner-management.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
Vendor
Name
Version
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 6.3VulDB Meta Temp Score: 6.3
VulDB Base Score: 7.3
VulDB Temp Score: 7.3
VulDB Vector: 🔍
VulDB Reliability: 🔍
NVD Base Score: 5.3
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: Improper authenticationCWE: CWE-287
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
05/30/2018 🔍05/30/2018 🔍
05/30/2018 🔍
05/31/2018 🔍
05/31/2018 🔍
02/10/2020 🔍
Sources
Advisory: labs.threatpress.comStatus: Not defined
CVE: CVE-2018-11579 (🔍)
GCVE (CVE): GCVE-0-2018-11579
GCVE (VulDB): GCVE-100-118395
Entry
Created: 05/31/2018 11:44Updated: 02/10/2020 08:41
Changes: 05/31/2018 11:44 (58), 02/10/2020 08:41 (4)
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.