CVE-2026-13754
Received Received - Intake

SQL Injection in Tickera WordPress Plugin

Publication date: 2026-07-16

Last updated on: 2026-07-16

Assigner: Wordfence

Description
The Tickera – Sell Tickets & Manage Events plugin for WordPress is vulnerable to generic SQL Injection via the 's' parameter in all versions up to, and including, 3.6.0.0 due to insufficient escaping on the user supplied parameter and lack of sufficient preparation on the existing SQL query. This makes it possible for authenticated attackers, with custom-level access and above, to append additional SQL queries into already existing queries that can be used to extract sensitive information from the database.

CVSS Scores

EPSS Scores

Probability:
Percentile:

Meta Information

Published
2026-07-16
Last Modified
2026-07-16
Generated
2026-07-16
AI Q&A
2026-07-16
EPSS Evaluated
N/A
NVD
CVE-2026-13754
EUVD
EUVD-2026-44887

Affected Vendors & Products

Showing 1 associated CPE
Vendor Product Version / Range
tickera tickera to 3.6.0.0 (inc)

Helpful Resources

Exploitability

CWE
CWE Icon
KEV
KEV Icon
CWE ID Description
CWE-89 The product constructs all or part of an SQL command using externally-influenced input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could modify the intended SQL command when it is sent to a downstream component. Without sufficient removal or quoting of SQL syntax in user-controllable inputs, the generated SQL query can cause those inputs to be interpreted as SQL instead of ordinary user data.

Attack-Flow Graph

AI Quick Actions

Instant insights powered by AI
Executive Summary

This vulnerability is a SQL Injection flaw in the Tickera WordPress plugin. It allows authenticated attackers with custom-level access or higher to inject malicious SQL code via the 's' parameter. The issue arises from insufficient input sanitization and lack of proper SQL query preparation, enabling attackers to manipulate database queries and potentially extract sensitive information.

Detection Guidance

This vulnerability can be detected by checking for unusual SQL query patterns or errors in logs. Look for requests containing the 's' parameter with appended SQL commands like UNION SELECT. Use tools like grep to search access logs for patterns such as 's=.*SELECT' or 's=.*UNION'.

Impact Analysis

If you use the Tickera plugin on your WordPress site, an attacker could exploit this flaw to access sensitive data stored in your database. This includes user information, payment details, or other confidential data. The attack requires authentication but could lead to significant data breaches or unauthorized access.

Compliance Impact

This vulnerability could lead to non-compliance with GDPR and HIPAA due to unauthorized data access. GDPR requires protecting personal data, and a breach could result in fines. HIPAA mandates safeguarding health information, and a similar breach could violate compliance requirements.

Mitigation Strategies

Immediately update the Tickera plugin to the latest version if available. If not, disable the plugin until a patch is released. Review database access logs for suspicious queries and restrict custom-level user access to only necessary personnel.

Chat Assistant

Ask questions about this CVE
Hi! I’m here to help you understand CVE-2026-13754. Ask me anything about the vulnerability, its impact, or mitigation strategies.
0/70

EPSS Chart