Filtered by vendor Wow-estore
Subscribe
Total
7 CVE
| CVE | Vendors | Products | Updated | CVSS v2 | CVSS v3 |
|---|---|---|---|---|---|
| CVE-2023-27452 | 1 Wow-estore | 1 Button Generator - Easily Button Builder | 2023-12-10 | N/A | 4.8 MEDIUM |
| Auth. (admin+) Stored Cross-Site Scripting (XSS) vulnerability in Wow-Company Button Generator – easily Button Builder plugin <= 2.3.3 versions. | |||||
| CVE-2022-29445 | 1 Wow-estore | 1 Popup Box | 2023-12-10 | 6.5 MEDIUM | 7.2 HIGH |
| Authenticated (administrator or higher role) Local File Inclusion (LFI) vulnerability in Wow-Company's Popup Box plugin <= 2.1.2 at WordPress. | |||||
| CVE-2022-29448 | 1 Wow-estore | 1 Herd Effects | 2023-12-10 | 4.0 MEDIUM | 4.9 MEDIUM |
| Authenticated (admin or higher user role) Local File Inclusion (LFI) vulnerability in Wow-Company's Herd Effects plugin <= 5.2 at WordPress. | |||||
| CVE-2022-0313 | 1 Wow-estore | 1 Float Menu | 2023-12-10 | 4.3 MEDIUM | 4.3 MEDIUM |
| The Float menu WordPress plugin before 4.3.1 does not have CSRF check in place when deleting menu, which could allow attackers to make a logged in admin delete them via a CSRF attack | |||||
| CVE-2021-24521 | 1 Wow-estore | 1 Side Menu | 2023-12-10 | 6.5 MEDIUM | 7.2 HIGH |
| The Side Menu Lite – add sticky fixed buttons WordPress plugin before 2.2.1 does not properly sanitize input values from the browser when building an SQL statement. Users with the administrator role or permission to manage this plugin could perform an SQL Injection attack. | |||||
| CVE-2021-24580 | 1 Wow-estore | 1 Side Menu | 2023-12-10 | 6.5 MEDIUM | 8.8 HIGH |
| The Side Menu Lite WordPress plugin before 2.2.6 does not sanitise user input from the List page in the admin dashboard before using it in SQL statement, leading to a SQL Injection issue | |||||
| CVE-2021-24348 | 1 Wow-estore | 1 Side Menu | 2023-12-10 | 6.5 MEDIUM | 7.2 HIGH |
| The menu delete functionality of the Side Menu – add fixed side buttons WordPress plugin before 3.1.5, available to Administrator users takes the did GET parameter and uses it into an SQL statement without proper sanitisation, validation or escaping, therefore leading to a SQL Injection issue | |||||