What is the CVSS score of CVE-2026-42774?

CVE-2026-42774 has a CVSS 3.1 base score of 9.3 (Critical). CVSS vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:N/A:L. EPSS exploitation probability: 0.0%.

Which versions of Crocoblock JetEngine are affected by CVE-2026-42774?

Crocoblock JetEngine WordPress plugin (versions ≤3.8.8.1) poses immediate data breach risk through a critical SQL injection vulnerability accessible without authentication.

How to fix or mitigate CVE-2026-42774?

Within 24 hours: Identify all WordPress installations running Crocoblock JetEngine ≤3.8.8.1; assess data sensitivity of affected systems and prioritize by exposure. Within 7 days: Disable the plugin on non-critical instances or deploy Web Application Firewall (WAF) rules blocking SQL injection patterns in JetEngine requests; apply database-level permission restrictions. Within 30 days: Monitor Patchstack advisory for vendor patch release; if available, upgrade immediately to patched version; if unavailable after 30 days, execute permanent remediation via plugin replacement or functionality retirement.

Crocoblock JetEngine CVE-2026-42774

EUVD-2026-31751 CRITICAL

SQL Injection (CWE-89)

2026-05-25 Patchstack

GHSA-g8m9-vcxf-8fwg

SQLi Jetengine

9.3

CVSS 3.1 · Vendor: Patchstack

Severity by source

Vendor (Patchstack) PRIMARY

9.3 CRITICAL

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

Primary rating from Vendor (Patchstack) · only source for this CVE.

CVSS VectorVendor: Patchstack

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

Attack Vector

Network

Attack Complexity

Low

Privileges Required

None

User Interaction

None

Scope

Changed

Confidentiality

High

Integrity

None

Availability

Low

Lifecycle Timeline

Analysis Generated

Jun 08, 2026 - 08:29 vuln.today

DescriptionCVE.org

Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection') vulnerability in Crocoblock JetEngine allows SQL Injection.

This issue affects JetEngine: from n/a through 3.8.8.1.

AnalysisAI

SQL injection in Crocoblock JetEngine (a WordPress plugin) through version 3.8.8.1 allows remote unauthenticated attackers to inject crafted SQL into backend queries, leading to high-impact confidentiality disclosure and limited availability impact with a scope change to other components. The flaw carries a CVSS 9.3 rating and was disclosed by Patchstack, but there is no public exploit identified at time of analysis and EPSS is very low at 0.03%.

Technical ContextAI

JetEngine is a popular Crocoblock plugin for WordPress used to build dynamic content, custom post types, listings, and meta fields, and it issues database queries against the WordPress MySQL/MariaDB backend. The root cause is CWE-89: Improper Neutralization of Special Elements used in an SQL Command, meaning user-controlled input is concatenated into SQL statements without proper parameterization or sanitization via wpdb->prepare or equivalent escaping. The affected CPE is cpe:2.3:a:crocoblock:jetengine:*:*:*:*:*:*:*:* covering all releases up to and including 3.8.8.1, and the scope-change flag (S:C) in the CVSS vector indicates the injected SQL can affect data or components beyond the plugin's own security context - typically the entire WordPress database including wp_users and authentication-relevant tables.

RemediationAI

No vendor-released patch identified at time of analysis from the provided data - the Patchstack advisory at https://patchstack.com/database/wordpress/plugin/jet-engine/vulnerability/wordpress-jetengine-plugin-3-8-8-1-sql-injection-vulnerability lists 3.8.8.1 as the last known-vulnerable version, so administrators should monitor that advisory and the Crocoblock changelog for a release above 3.8.8.1 and upgrade as soon as it is published. Until a fixed release is available, deploy Patchstack's vPatch or a WAF rule that blocks SQL metacharacters in JetEngine REST and AJAX endpoints (commonly under /wp-json/jet-engine/ and admin-ajax.php with action parameters containing 'jet_engine'), accepting that overly broad rules may break legitimate listing queries and dynamic filtering. Compensating controls include restricting access to /wp-admin and admin-ajax.php to known IPs, enforcing the WordPress database user's privileges to SELECT/INSERT/UPDATE/DELETE on its own schema only (no FILE or SUPER), and enabling query logging to detect probing - note that disabling JetEngine entirely will break any site that depends on its custom post types and listings.