CVE-2026-121858

Event Tickets with Ticket Scanner <= 3.2.8 - Authenticated (Custom+) SQL Injection

2026-11-05 00:00
Mokksh Parekh

Strategic Overview

Status
Patched in 3.2.9
Affected Plugin
Event Tickets with Ticket Scanner
Affected Version
<= 3.2.8
CVSS
6.5Medium
Weakness type
CWE-89 · Improper Neutralization of Special Elements used in an SQL Command
CVE
CVE-2026-121858
View all Event Tickets with Ticket Scanner vulnerabilities

At a glance

CVE-2026-121858 is a medium-severity Improper Neutralization of Special Elements used in an SQL Command vulnerability in the Event Tickets with Ticket Scanner WordPress plugin, affecting versions <= 3.2.8. It carries a CVSS score of 6.5 (reachable over the network; low attack complexity; high confidentiality impact). Exploitation requires an authenticated account at Custom level or above. The issue is fixed in version 3.2.9; sites on affected versions should update now. Disclosed November 2026, reported by Mokksh Parekh.

Vulnerability Overview

The Event Tickets with Ticket Scanner plugin for WordPress is vulnerable to SQL Injection in all versions up to, and including, 3.2.8. This is 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 to append additional SQL queries into already existing queries that can be used to extract sensitive information from the database.

Technical Analysis

The vector marks this flaw as remotely reachable over the network, with low attack complexity — no special timing or configuration is needed, and no interaction from a victim user. A successful exploit has high impact on confidentiality.

CWE-89: Improper Neutralization of Special Elements used in an SQL Command

Reaching this weakness in Event Tickets with Ticket Scanner <= 3.2.8 takes an account at Custom level or above. SQL injection happens when request data is concatenated into a query instead of being bound as a parameter, letting an attacker change the structure of the statement rather than just its values.

A working injection can read any table the database user can see, which on a WordPress install means user records, password hashes and session or API secrets stored in options. For Event Tickets with Ticket Scanner the fix is 3.2.9: builds <= 3.2.8 are affected, anything from 3.2.9 onward is not.

Remediation

Update to version 3.2.9, or a newer patched version

How does WordSec protect against this?

An attacker needs Custom access first, so the firewall sees the attempt as traffic from a logged-in account: WordSec's web application firewall inspects request payloads before WordPress loads them. None of that substitutes for the fix: Event Tickets with Ticket Scanner 3.2.9 closes this, and updating the plugin is the step that ends it.

  • Firewall
  • Alerts

External References

https://www.cve.org/CVERecord?id=CVE-2026-121858https://www.wordfence.com/threat-intel/vulnerabilities/id/10929cb2-9e91-4253-a1c2-337e5ff5174ehttps://nvd.nist.gov/vuln/detail/CVE-2026-121858

Related records

Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C