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

CVE-2026-56068 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.2%.

Which versions of JetEngine are affected by CVE-2026-56068?

Crocoblock JetEngine, a widely deployed WordPress plugin for dynamic content management, contains a critical SQL injection vulnerability (CVE-2026-56068, CVSS 9.3) allowing unauthenticated remote…

How to fix or mitigate CVE-2026-56068?

Within 24 hours: Inventory all WordPress instances, identify JetEngine installations at version 3.8.10.2 or earlier, and immediately disable the plugin on affected systems. Within 7 days: Contact Crocoblock for patch timeline; if unavailable, implement WAF rules blocking SQL injection patterns on all WordPress entry points and restrict database network access to application servers only. Within 30 days: Replace JetEngine with alternative dynamic-content solutions or deploy the patched version once released by Crocoblock.

JetEngine CVE-2026-56068

EUVD-2026-39721 CRITICAL

SQL Injection (CWE-89)

2026-06-26 audit@patchstack.com

GHSA-6345-fj22-6hh8

WordPress SQLi Wordpress Plugin

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

vuln.today AI

8.2 HIGH

Unauthenticated network SQLi (AV:N/AC:L/PR:N/UI:N) gives high database read (C:H) and limited write potential (I:L); scope kept U as injection stays within the WordPress DB context.

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

4.0 AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:L/VA:N/SC:N/SI:N/SA:N

Primary rating from Vendor (patchstack).

CVSS VectorVendor: patchstack

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 26, 2026 - 15:56 vuln.today

DescriptionCVE.org

Unauthenticated SQL Injection in JetEngine <= 3.8.10.2 versions.

AnalysisAI

SQL injection in the Crocoblock JetEngine WordPress plugin (versions 3.8.10.2 and earlier) lets remote unauthenticated attackers inject crafted SQL into backend database queries (CWE-89), per the CVSS:3.1 vector with PR:N/UI:N. The flaw carries a 9.3 critical score driven by network reachability, no required privileges, and a changed scope exposing the underlying WordPress database. No public exploit identified at time of analysis, and the issue is not listed in CISA KEV, but the unauthenticated, low-complexity nature makes it a high-priority patching target for any site running this widely deployed dynamic-content plugin.

Technical ContextAI

JetEngine is a Crocoblock plugin for WordPress that builds dynamic listings, custom post types, custom meta fields, and query-driven content, typically alongside page builders like Elementor. The root cause is CWE-89 (SQL Injection): user-controllable input reaches a database query without proper parameterization or sanitization, allowing the attacker's data to be interpreted as SQL. Because WordPress queries run against the shared site database (wp_users, wp_options, wp_posts, etc.), a successful injection can read arbitrary stored data including credentials and secrets. No exact vulnerable parameter or endpoint is named in the available intelligence; the affected component is identified only by plugin name and the affected version ceiling (<= 3.8.10.2).

RemediationAI

Upgrade JetEngine to a fixed release above 3.8.10.2 as published by Crocoblock; the exact patched version is not included in the available input data, so confirm it directly via the Patchstack advisory (https://patchstack.com/database/wordpress/plugin/jet-engine/vulnerability/wordpress-jetengine-plugin-3-8-10-2-sql-injection-vulnerability) and the Crocoblock changelog before deploying. If immediate patching is not possible, deploy a WAF or virtual patch (Patchstack and similar WordPress firewalls offer SQLi rule coverage) to filter injection payloads against JetEngine endpoints - accepting that WAF rules can be bypassed and may cause false positives on legitimate query parameters. As a stronger interim control, restrict or disable the affected JetEngine query/listing functionality if the site does not require it, and ensure the database user used by WordPress has least-privilege rights to limit the blast radius of any successful read; note this does not stop the injection itself, only its scope.