CVE-2026-121858 Event Tickets with Ticket Scanner < 3.2.9 - Authenticated SQLi via DataTables Search
Medium 6.3
Published
Updated
Check this codebase for CVE-2026-121858 and fix it if it is affected.
What it is: CVE-2026-121858 is a medium-severity vulnerability in Unknown Event Tickets with Ticket Scanner, published on 7 Nov 2026.
Exploitation: There is no known exploitation of CVE-2026-121858 in the wild and no public exploit code.
Affected product: Unknown Event Tickets with Ticket Scanner. No package-level version data is available, so check the vendor advisory linked from the reference page.
Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.
Reference: https://insights.sbomify.com/CVE-2026-121858/ (Markdown: https://insights.sbomify.com/CVE-2026-121858/index.md)
- Exploited in the wild
- Not known
- Fix
- None listed
What is CVE-2026-121858?
CVE-2026-121858 is a medium-severity vulnerability in Unknown Event Tickets with Ticket Scanner, published on 7 Nov 2026.
Official 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.
Weakness: CWE-89
Which versions are affected by CVE-2026-121858?
How do I fix CVE-2026-121858?
No fix has been published for CVE-2026-121858 yet. Limit exposure of the affected software until one is available.
Is CVE-2026-121858 being exploited?
There is no known exploitation of CVE-2026-121858 in the wild and no public exploit code.
Sources
Also known as GHSA-63f4-qh3h-4mx3.