Attack Chain

1. An unauthenticated attacker identifies a WordPress site using JetEngine plugin version 3.8.6.1 or earlier with at least one Custom Content Type configured with a public REST GET endpoint.
2. The attacker crafts a malicious HTTP GET request to the CCT REST API endpoint, including a SQL injection payload within the _cct_search parameter.
3. The WordPress REST API receives the request and calls the wp_unslash() function to strip the wp_magic_quotes() protection from the $_GET array, allowing the SQL injection payload to pass unfiltered.
4. The JetEngine plugin uses sprintf() to directly interpolate the unsanitized _cct_search parameter into a SQL query string.
5. The injected SQL code is executed against the WordPress database.
6. The attacker leverages the SQL injection to extract sensitive information such as user credentials, API keys, or other confidential data stored in the database.
7. The attacker may further exploit the vulnerability to modify or delete data within the database, potentially leading to a complete compromise of the WordPress site.
8. The attacker uses the compromised site as a beachhead for further attacks against the wider network infrastructure.

Impact

Successful exploitation of this SQL injection vulnerability (CVE-2026-4352) can lead to the complete compromise of a WordPress website. An attacker can gain access to sensitive data, including user credentials, configuration files, and other confidential information stored within the database. This can result in data breaches, financial loss, and reputational damage. Given the widespread use of WordPress and the JetEngine plugin, a large number of websites are potentially vulnerable.

Recommendation

• Upgrade the JetEngine plugin to the latest version (greater than 3.8.6.1) to patch CVE-2026-4352.
• Deploy the Sigma rule JetEngine_CCT_SQLi_Detection to detect attempts to exploit this vulnerability via suspicious characters in the cs-uri-query field within web server logs.
• Disable public REST GET endpoints for CCTs unless absolutely necessary to reduce the attack surface.
• Review and sanitize all user-supplied input before using it in database queries to prevent SQL injection vulnerabilities.