Tickera Sell Tickets Manage Events
Monthly
SQL injection in the Tickera - Sell Tickets & Manage Events WordPress plugin (all versions through 3.6.0.1) allows authenticated attackers holding the plugin's Staff role to append arbitrary SQL to existing queries via the unescaped 'tc_event_filter' parameter, extracting sensitive data from the WordPress database. The exposure is enabled by the plugin's own add_required_capabilities() function, which grants the custom Staff role the edit_tc_tickets_instances capability - meaning any staff-level account can reach the vulnerable tc_tickets_instances admin list screen and trigger the injection. No public exploit or CISA KEV listing has been identified at time of analysis, but the low authentication bar (staff role, not admin) and high confidentiality impact make this a meaningful risk for multi-tenant event-ticketing deployments.
Stored Cross-Site Scripting in the Tickera - Sell Tickets & Manage Events WordPress plugin (all versions through 3.6.0.0) allows authenticated contributors to inject persistent malicious scripts via the price_wrapper shortcode attribute, due to missing sanitization and output escaping in class.shortcodes.php. A compromised or malicious contributor account can plant the payload in any page or post, where it executes against visiting victims - but only those who carry the referenced ticket ID in their cart cookie, materially narrowing the realistic victim pool. No active exploitation has been confirmed in CISA KEV, and no EPSS data was provided in the intelligence feed.
SQL Injection in the Tickera - Sell Tickets & Manage Events WordPress plugin (all versions through 3.6.0.0) permits authenticated attackers holding a custom-level role or above to append arbitrary SQL to existing queries via the unsanitized 's' search parameter, enabling full database read access. The vulnerability originates in the better-attendees-and-tickets addon (index.php lines 50, 485, and 502) and is confirmed by Wordfence with source code evidence. No active exploitation is confirmed (no CISA KEV listing) and no public exploit has been identified at time of analysis, keeping real-world urgency moderate despite the High confidentiality impact.
SQL injection in the Tickera - Sell Tickets & Manage Events WordPress plugin (all versions through 3.6.0.1) allows authenticated attackers holding the plugin's Staff role to append arbitrary SQL to existing queries via the unescaped 'tc_event_filter' parameter, extracting sensitive data from the WordPress database. The exposure is enabled by the plugin's own add_required_capabilities() function, which grants the custom Staff role the edit_tc_tickets_instances capability - meaning any staff-level account can reach the vulnerable tc_tickets_instances admin list screen and trigger the injection. No public exploit or CISA KEV listing has been identified at time of analysis, but the low authentication bar (staff role, not admin) and high confidentiality impact make this a meaningful risk for multi-tenant event-ticketing deployments.
Stored Cross-Site Scripting in the Tickera - Sell Tickets & Manage Events WordPress plugin (all versions through 3.6.0.0) allows authenticated contributors to inject persistent malicious scripts via the price_wrapper shortcode attribute, due to missing sanitization and output escaping in class.shortcodes.php. A compromised or malicious contributor account can plant the payload in any page or post, where it executes against visiting victims - but only those who carry the referenced ticket ID in their cart cookie, materially narrowing the realistic victim pool. No active exploitation has been confirmed in CISA KEV, and no EPSS data was provided in the intelligence feed.
SQL Injection in the Tickera - Sell Tickets & Manage Events WordPress plugin (all versions through 3.6.0.0) permits authenticated attackers holding a custom-level role or above to append arbitrary SQL to existing queries via the unsanitized 's' search parameter, enabling full database read access. The vulnerability originates in the better-attendees-and-tickets addon (index.php lines 50, 485, and 502) and is confirmed by Wordfence with source code evidence. No active exploitation is confirmed (no CISA KEV listing) and no public exploit has been identified at time of analysis, keeping real-world urgency moderate despite the High confidentiality impact.