CVE-2026-4352: JetEngine <= 3.8.6.1 - Unauthenticated SQL Injection via '_cct_search' Parameter
The JetEngine plugin for WordPress is vulnerable to SQL Injection via the Custom Content Type (CCT) REST API search endpoint in all versions up to, and including, 3.8.6.1. This is due to the cctsearch parameter being interpolated directly into a SQL query string via sprintf() without sanitization or use of $wpdb->prepare(). WordPress REST API's wpunslash() call on $GET strips the wpmagicquotes() protection, allowing single-quote-based injection. 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. The Custom Content Types module must be enabled with at least one CCT configured with a public REST GET endpoint for exploitation.
Affected Software
Event History
Frequently Asked Questions
What is the severity of CVE-2026-4352?
CVE-2026-4352 is classified as a critical severity vulnerability due to its potential for unauthenticated SQL Injection.
How do I fix CVE-2026-4352?
To fix CVE-2026-4352, update the JetEngine plugin to version 3.8.6.2 or later.
Which versions of JetEngine are affected by CVE-2026-4352?
CVE-2026-4352 affects all versions of JetEngine up to and including 3.8.6.1.
What kind of attack can CVE-2026-4352 facilitate?
CVE-2026-4352 can facilitate unauthorized SQL Injection attacks via the '_cct_search' parameter.
Who is the vendor responsible for CVE-2026-4352?
The vendor responsible for CVE-2026-4352 is Crocoblock, the developer of the JetEngine plugin.