dbcve.org
SQL InjectionWeakness · CWE-89

CVE-2026-9848

HIGH · 7.5 CVSS v3.1 Published 2026-06-13
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
84/100
Remediation priority · High
Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

The WP Ticket plugin for WordPress versions up to 6.0.4 contains a SQL Injection vulnerability in its search functionality. The plugin's `wp_ticket_com_posts_request()` filter hook passes the unsanitized WordPress search parameter `s` (already unwrapped from magic quotes by WP_Query) directly into a SQL LIKE clause within a UNION sub-SELECT query, without using `$wpdb->prepare()` or any escaping, allowing unauthenticated attackers to inject arbitrary SQL queries.

MitigationUpdate to the latest version of the WP Ticket plugin when available, and immediately apply parameterized queries using `$wpdb->prepare()` with proper placeholders (e.g., `%s`) for the search parameter in the `emd_author_search_results()` function.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Verify WP Ticket plugin is installed
    In WordPress admin, go to Plugins > Installed Plugins and look for 'WP Ticket' or 'WP Ticket Enterprise' in the list. Note the version number displayed below the plugin name.
    Affected if The plugin is installed and the version is 6.0.4 or lower
  2. Confirm the vulnerable function exists in the codebase
    Navigate to the plugin directory (usually wp-content/plugins/wp-ticket) and search for the function 'emd_author_search_results' in PHP files, or use grep: grep -r 'function emd_author_search_results' .
    Affected if The function emd_author_search_results exists in the plugin code, indicating the vulnerable code is present
  3. Check for the unsanitized search parameter usage
    Examine the plugin files for code that uses the WordPress search parameter 's' in a SQL query without $wpdb->prepare. Look for patterns like $wpdb->prepare missing near SQL LIKE clauses containing the search term.
    Affected if The plugin contains SQL queries using the search parameter without prepare() or escaping, meaning the injection point exists
  4. Verify search functionality is accessible to unauthenticated users
    Visit your WordPress site and confirm the search feature works without logging in. The vulnerability is exploitable by unauthenticated attackers through the standard WordPress search form.
    Affected if The site search functionality is publicly accessible, which is the default WordPress behavior

You are affected if the WP Ticket plugin version is 6.0.4 or lower and the plugin with its vulnerable search function is installed and active on your WordPress site.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Update to the latest version of the WP Ticket plugin when available, and immediately apply parameterized queries using `$wpdb->prepare()` with proper placeholders (e.g., `%s`) for the search parameter in the `emd_author_search_results()` function.

Recommended fix Moderate confidence

Latest version of WP Ticket plugin after 6.0.4 (verify exact version on WordPress plugin repository)

  1. Identify the current installed version of the WP Ticket plugin for WordPress
  2. Navigate to Plugins > Installed Plugins in WordPress admin dashboard
  3. Locate the WP Ticket plugin and note the current version number
  4. Check the WordPress plugin repository at plugins.trac.wordpress.org for the WP Ticket plugin
  5. Look for version releases after 6.0.4 which should contain the security fix
  6. Upgrade to the latest available version of the WP Ticket plugin that includes the SQL injection fix
  7. After upgrading, verify the fix by checking that the plugin no longer uses unsanitized input in the emd_author_search_results() function

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing3.0 h
  • Review / QA1.0 h
8.0 hours of engineering $1,390
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,224.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-9848 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-9848 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data