CVE-2026-9848: WP Ticket <= 6.0.4 - Unauthenticated SQL Injection via WordPress Search 's' Parameter
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 postsrequest filter with wpticketcompostsrequest(), which calls emdauthorsearchresults() when the current request is an unauthenticated front-end search. That function reads $query->queryvars['s'] — already wpunslash()'d by WPQuery::parsequery(), so wpmagicquotes 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.
Affected Software
Event History
Frequently Asked Questions
What is the severity of CVE-2026-9848?
CVE-2026-9848 has a high severity rating of 7.5.
What types of attacks can CVE-2026-9848 be used for?
CVE-2026-9848 enables unauthenticated SQL Injection attacks via the WordPress search 's' parameter.
How do I fix CVE-2026-9848?
To mitigate CVE-2026-9848, users should update the WP Ticket plugin to a version after 6.0.4.
What versions of WP Ticket are affected by CVE-2026-9848?
CVE-2026-9848 affects all WP Ticket versions up to and including 6.0.4.
Is authentication required to exploit CVE-2026-9848?
No, CVE-2026-9848 can be exploited without authentication.