# CVE-2026-9848: WP Ticket <= 6.0.4 - Unauthenticated SQL Injection via WordPress Search 's' Parameter

> Unauthenticated attackers can exploit SQL injection in the WP Ticket plugin to extract sensitive database information via the search parameter.

- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 13 Jun 2026
- **Updated:** 15 Jun 2026
- **Also known as:** GHSA-cmwh-2j7f-4vh3

## What is CVE-2026-9848?

CVE-2026-9848 is a high-severity SQL injection vulnerability in emarket-design Customer Support Ticket System & Helpdesk, published on 13 Jun 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The WP Ticket plugin for WordPress is vulnerable to SQL Injection via the WordPress search query parameter (`s`) in versions up to, and including, 6.0.4 The plugin hooks WordPress's `posts_request` filter with `wp_ticket_com_posts_request()`, which calls `emd_author_search_results()` when the current request is an unauthenticated front-end search. That function reads `$query->query_vars['s']` — already wp_unslash()'d by `WP_Query::parse_query()`, so wp_magic_quotes protection has been stripped — and concatenates the raw value into a SQL `LIKE` clause inside a UNION sub-SELECT appended to the main query, with no `$wpdb->prepare()` or escaping. This makes it possible for unauthenticated attackers to append additional SQL queries into already-existing queries that can be used to extract sensitive information from the database.

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

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


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

No fix has been published for CVE-2026-9848 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-9848 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-9848 exists.

Public exploit code:

- CVE-2026-9848 is an Unauthenticated SQL Injection (SQLi) vulnerability affecting the WP Ticket (Customer Support Ticket System & Helpdesk) plugin for WordPress up to and including version 6.0.4. (github_poc): https://github.com/aj2108/CVE-2026-9848
- WP Ticket <= 6.0.4 - SQL Injection (nuclei): http/cves/2026/CVE-2026-9848.yaml

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-9848 and fix it if it is affected.

What it is: CVE-2026-9848 is a high-severity SQL injection vulnerability in emarket-design Customer Support Ticket System & Helpdesk, published on 13 Jun 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-9848 exists.

Affected product: emarket-design Customer Support Ticket System & Helpdesk. 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-9848/ (Markdown: https://insights.sbomify.com/CVE-2026-9848/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-9848
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-9848
- OSV: https://osv.dev/vulnerability/CVE-2026-9848

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-9848/
Summaries are generated and may contain mistakes; the official description above is the record.