Filtered by vendor Tickera
Subscribe
Total
6 CVE
| CVE | Vendors | Products | Updated | CVSS v2 | CVSS v3 |
|---|---|---|---|---|---|
| CVE-2024-10263 | 1 Tickera | 1 Tickera | 2024-11-08 | N/A | 7.3 HIGH |
| The Tickera – WordPress Event Ticketing plugin for WordPress is vulnerable to arbitrary shortcode execution in all versions up to, and including, 3.5.4.4. This is due to the software allowing users to execute an action that does not properly validate a value before running do_shortcode. This makes it possible for unauthenticated attackers to execute arbitrary shortcodes. | |||||
| CVE-2024-5860 | 1 Tickera | 1 Tickera | 2024-07-05 | N/A | 4.3 MEDIUM |
| The Tickera – WordPress Event Ticketing plugin for WordPress is vulnerable to unauthorized loss of data due to a missing capability check on the tc_dl_delete_tickets AJAX action in all versions up to, and including, 3.5.2.8. This makes it possible for authenticated attackers, with Subscriber-level access and above, to delete all tickets associated with events. | |||||
| CVE-2024-35729 | 1 Tickera | 1 Tickera | 2024-06-12 | N/A | 8.8 HIGH |
| Missing Authorization vulnerability in Tickera.This issue affects Tickera: from n/a through 3.5.2.6. | |||||
| CVE-2023-41861 | 1 Tickera | 1 Restrict | 2024-02-28 | N/A | 6.1 MEDIUM |
| Unauth. Reflected Cross-Site Scripting (XSS) vulnerability in Restrict plugin <= 2.2.4 versions. | |||||
| CVE-2022-4549 | 1 Tickera | 1 Tickera | 2024-02-28 | N/A | 4.3 MEDIUM |
| The Tickera WordPress plugin before 3.5.1.0 does not have CSRF check in place when updating its settings, which could allow attackers to make a logged-in admin change them via a CSRF attack. | |||||
| CVE-2021-24797 | 1 Tickera | 1 Tickera | 2024-02-28 | 4.3 MEDIUM | 6.1 MEDIUM |
| The Tickera WordPress plugin before 3.4.8.3 does not properly sanitise and escape the Name fields of booked Events before outputting them in the Orders admin dashboard, which could allow unauthenticated users to perform Cross-Site Scripting attacks against admins. | |||||