Vulnerabilities > TRI
| DATE | CVE | VULNERABILITY TITLE | RISK |
|---|---|---|---|
| 2024-06-14 | CVE-2024-1295 | Unspecified vulnerability in TRI the Events Calendar The events-calendar-pro WordPress plugin before 6.4.0.1, The Events Calendar WordPress plugin before 6.4.0.1 does not prevent users with at least the contributor role from leaking details about events they shouldn't have access to. | 6.5 |
| 2024-02-12 | CVE-2023-7233 | Cross-site Scripting vulnerability in TRI Gigpress The GigPress WordPress plugin through 2.3.29 does not sanitise and escape some of its settings, which could allow high privilege users such as admin to perform Stored Cross-Site Scripting attacks even when the unfiltered_html capability is disallowed (for example in multisite setup) | 4.8 |
| 2023-02-27 | CVE-2023-0381 | Unspecified vulnerability in TRI Gigpress The GigPress WordPress plugin through 2.3.28 does not validate and escape some of its shortcode attributes before using them in SQL statement/s, which could allow any authenticated users, such as subscriber to perform SQL Injection attacks | 8.8 |
| 2022-12-27 | CVE-2020-36626 | Cross-site Scripting vulnerability in TRI Panel Builder A vulnerability classified as critical has been found in Modern Tribe Panel Builder Plugin. | 6.1 |
| 2022-01-24 | CVE-2021-25028 | Unspecified vulnerability in TRI Event Tickets The Event Tickets WordPress plugin before 5.2.2 does not validate the tribe_tickets_redirect_to parameter before redirecting the user to the given value, leading to an arbitrary redirect issue | 6.1 |
| 2019-09-08 | CVE-2019-16120 | Improper Neutralization of Formula Elements in a CSV File vulnerability in TRI Event Tickets CSV injection in the event-tickets (Event Tickets) plugin before 4.10.7.2 for WordPress exists via the "All Post> Ticketed > Attendees" Export Attendees feature. | 8.8 |
| 2019-08-28 | CVE-2015-9353 | SQL Injection vulnerability in TRI Gigpress The gigpress plugin before 2.3.11 for WordPress has SQL injection in the admin area, a different vulnerability than CVE-2015-4066. | 7.2 |