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.
Security readout for executives and security teams
Plain-English summary
CVE-2026-13754 affects the Tickera WordPress event-ticketing plugin. A logged-in staff-level user or higher may be able to manipulate a search parameter to read sensitive database information. This is not rated critical because authentication is required, but it matters for sites that give many people staff access.
Executive priority
Treat this as a near-term remediation item for WordPress ticketing sites. Prioritize sites handling customer, attendee, order, or payment-adjacent data, and reduce unnecessary staff access while waiting for confirmed vendor fix guidance.
Technical view
The flaw is SQL injection in the Tickera plugin's 's' parameter through insufficient escaping and query preparation. The CVSS 3.1 score is 6.5, with network access, low complexity, low privileges, no user interaction, and high confidentiality impact. The cited code paths are in the better-attendees-and-tickets add-on file.
Likely exposure
WordPress sites running Tickera – Sell Tickets & Manage Events up to and including 3.6.0.0 are the stated exposure, especially where staff or custom-level accounts are broadly assigned.
Exploitation context
The bundle does not cite CISA KEV or active exploitation. Exploitation requires an authenticated account with custom-level access or higher, limiting internet-wide risk but increasing insider, compromised-account, and overprivileged-user risk.
Researcher notes
Evidence supports authenticated SQL injection and confidentiality impact, but the supplied bundle does not name a fixed version or show active exploitation. Use the Trac references to confirm vulnerable query construction and the changeset before making firm remediation claims.
Mitigation direction
Identify sites running Tickera versions up to and including 3.6.0.0.
Check Tickera or WordPress plugin guidance for the fixed release before upgrading.
Restrict staff and custom-level access to trusted users only.
Review recently created staff accounts and remove unnecessary privileges.
Monitor WordPress and database logs for unusual authenticated search activity.
Validation and detection
Confirm installed Tickera plugin version across WordPress assets.
Verify whether the better-attendees-and-tickets add-on is present and enabled.
Review role assignments for staff, custom-level, administrator, and equivalent accounts.
Check security advisories for a named fixed version or vendor workaround.
Inspect logs for suspicious authenticated requests involving the 's' parameter.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
cwe · medium confidence lookup
CWE-89: Database access and collection lookup
Injection into data stores can inform collection, data access, and exfiltration detection reviews. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
The CVE wording references database injection or access, so collection and exfiltration review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
CWE-89 · source CWE mapping
Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection')
Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection') represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.