Filtered by vendor Wp-eventmanager
Subscribe
Total
6 CVE
CVE | Vendors | Products | Updated | CVSS v2 | CVSS v3 |
---|---|---|---|---|---|
CVE-2023-52118 | 1 Wp-eventmanager | 1 Wp Event Manager | 2024-02-06 | N/A | 5.4 MEDIUM |
Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') vulnerability in WP Event Manager WP User Profile Avatar allows Stored XSS.This issue affects WP User Profile Avatar: from n/a through 1.0. | |||||
CVE-2023-6384 | 1 Wp-eventmanager | 1 User Profile Avatar | 2024-02-05 | N/A | 4.3 MEDIUM |
The WP User Profile Avatar WordPress plugin before 1.0.1 does not properly check for authorisation, allowing authors to delete and update arbitrary avatar | |||||
CVE-2023-49181 | 1 Wp-eventmanager | 1 Wp Event Manager | 2024-02-05 | N/A | 5.4 MEDIUM |
Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') vulnerability in WP Event Manager WP Event Manager – Events Calendar, Registrations, Sell Tickets with WooCommerce allows Stored XSS.This issue affects WP Event Manager – Events Calendar, Registrations, Sell Tickets with WooCommerce: from n/a through 3.1.40. | |||||
CVE-2022-1474 | 1 Wp-eventmanager | 1 Wp Event Manager | 2024-02-04 | 4.3 MEDIUM | 6.1 MEDIUM |
The WP Event Manager WordPress plugin before 3.1.28 does not sanitise and escape its search before outputting it back in an attribute on the event dashboard, leading to a Reflected Cross-Site Scripting | |||||
CVE-2021-24810 | 1 Wp-eventmanager | 1 Wp Event Manager | 2024-02-04 | 3.5 LOW | 4.8 MEDIUM |
The WP Event Manager WordPress plugin before 3.1.23 does not escape some of its Field Editor settings when outputting them, allowing high privilege users to perform Cross-Site Scripting attacks even when the unfiltered_html capability is disallowed | |||||
CVE-2021-24252 | 1 Wp-eventmanager | 1 Event Banner | 2024-02-04 | 6.5 MEDIUM | 7.2 HIGH |
The Event Banner WordPress plugin through 1.3 does not verify the uploaded image file, allowing admin accounts to upload arbitrary files, such as .exe, .php, or others executable, leading to RCE. Due to the lack of CSRF check, the issue can also be used via such vector to achieve the same result, or via a LFI as authorisation checks are missing (but would require WP to be loaded) |