Event Tickets with Ticket Scanner < 3.2.9 - Authenticated SQLi via DataTables Search
- Exploited
- No known exploitation
- Fix
- Fixed in 3.2.9
- Who is exposed
- Not reported
Do first: Upgrade to a fixed version: 3.2.9.
- Last modified
- FIRST's estimate of the chance attackers exploit it in the next 30 days, updated daily.What do these mean? →
- 0.16% · 4th percentile
- A 0-100 score for how much a CVE matters across the industry: exploitation, exposure, how widely the software is used, severity and whether a fix exists.What do these mean? →
- 9/100 · provisional
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
- Exploitation: none
- Automatable: no
- Technical impact: partial
Summary
The Event Tickets with Ticket Scanner WordPress plugin contains an SQL injection flaw in several admin listings, where a search value is not properly escaped before it is used in database queries. An attacker who already has access to the plugin's admin area (by default, administrators, or any role granted access in its settings) can use it to run SQL injection attacks.
Written by anthropic/claude-haiku-5.5 from the sources below. Verify against them.
Read the original description
The Event Tickets with Ticket Scanner WordPress plugin before 3.2.9 does not properly escape a search value before using it in SQL queries in several of its admin listings, allowing users with access to its admin area (administrators by default, or any role granted access in its settings) to perform SQL injection attacks.
cve.now Index
- Exploitation0/40No signal
- Exposure3/25Reachable over the network · Unknown: No advisory context yet
- Reach?/20Unknown. No tracked technology or package matched
- Severity6.3/10CVSS 6.3
- No patch0/5No signal
What would change the score
- Would score about 64 if added to CISA KEV
- Would score about 59 if CISA's SSVC rates exploitation active
- Would score about 28 if advisories confirm default setups are exposed
What to do
Upgrade to a fixed version: 3.2.9.
Timeline
- CVE published
- First seen by cve.now
- CISA SSVC assessment
Exploitation: none · Automatable: no · Technical impact: partial
- Record last updated
Affected versions
- Unknown Event Tickets with Ticket Scanner
fixed in 3.2.9
Evidence 1
- Exploit
Corrections
None so far.
Something wrong on this page? Report an error. Every fix is listed here.
Questions about CVE-2026-121858
Is CVE-2026-121858 being exploited?
It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.Source: cve.now feed data
Which versions are affected by CVE-2026-121858?
Event Tickets with Ticket Scanner: before 3.2.9.Source: cve.now feed data
How do I fix CVE-2026-121858?
Upgrade to a fixed version: 3.2.9.Source: cve.now feed data