dbcve.org
SQL InjectionWeakness · CWE-89

CVE-2026-4352

HIGH · 7.5 CVSS v3.1 Published 2026-04-14
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
84/100
Remediation priority · High
Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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 `_cct_search` parameter being interpolated directly into a SQL query string via `sprintf()` without sanitization or use of `$wpdb->prepare()`. WordPress REST API's `wp_unslash()` call on `$_GET` strips the `wp_magic_quotes()` 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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

The JetEngine plugin for WordPress contains an unauthenticated SQL injection vulnerability in the Custom Content Type REST API search endpoint. The `_cct_search` parameter is passed through WordPress's `wp_unslash()` function (which removes magic quotes protection) and then directly interpolated into an SQL query string via `sprintf()` without sanitization or use of `$wpdb->prepare()`, allowing unauthenticated attackers to inject arbitrary SQL commands.

MitigationUpdate JetEngine to version 3.8.7 or later to receive the patched code that properly sanitizes or parameterizes the `_cct_search` parameter. Alternatively, if the Custom Content Types module is not required, disable it entirely or ensure no CCTs are configured with public REST GET endpoints.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

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

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Check JetEngine plugin version
    Navigate to Plugins > Installed Plugins in WordPress admin, locate JetEngine, and note the installed version number. Alternatively, check the version in the plugin header file via file system access.
    Affected if Version is lower than 3.8.7 (e.g., 3.8.6, 3.8.5, earlier versions)
  2. Verify Custom Content Types module is enabled
    In WordPress admin, go to JetEngine > Dashboard and check if the Custom Content Types module toggle is enabled. Alternatively, check for the existence of CCT post types via WP CLI: wp post_type list --post_type=cct* or inspect the database table wp_options for jet_cct_options.
    Affected if The Custom Content Types module is active or any CCT post types exist in the system
  3. Confirm public REST API endpoints exist for CCTs
    Access the REST API endpoint for CCTs by visiting a URL such as /wp-json/jet-engine/cct/ or /index.php?rest_route=/jet-engine/cct/ and check for public (non-authenticated) GET access. Alternatively, inspect the CCT configuration in JetEngine > Custom Content Types and verify the REST API Support setting is enabled.
    Affected if CCTs are configured with public REST GET endpoint support and are accessible without authentication
  4. Test for vulnerable parameter exposure
    Send a crafted GET request to the CCT search endpoint, for example: GET /wp-json/jet-engine/cct/<cct_name>/?_cct_search=test' (adding a single quote). Check if the response returns a database error indicating SQL syntax issues.
    Affected if The endpoint is accessible and responds with SQL error messages or unexpected behavior when the _cct_search parameter contains SQL metacharacters

User is affected if JetEngine version is below 3.8.7 AND the Custom Content Types module is enabled with at least one CCT configured with public REST API access, as this allows unauthenticated SQL injection via the _cct_search parameter.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Update JetEngine to version 3.8.7 or later to receive the patched code that properly sanitizes or parameterizes the `_cct_search` parameter. Alternatively, if the Custom Content Types module is not required, disable it entirely or ensure no CCTs are configured with public REST GET endpoints.

Recommended fix Moderate confidence

JetEngine version later than 3.8.6.1 (check crocoblock.com for the latest stable release)

  1. 1. Log in to the WordPress admin dashboard
  2. 2. Navigate to Plugins > Installed Plugins
  3. 3. Find JetEngine in the plugin list
  4. 4. If an update is available, click 'Update Now' to update to the latest version
  5. 5. Alternatively, download the latest version of JetEngine from crocoblock.com or the WordPress plugin repository and upload it manually
  6. 6. Verify the update was successful by checking the plugin version after updating
  7. 7. Ensure the Custom Content Types module settings are reviewed - confirm only necessary CCTs have public REST API endpoints enabled
Caveat Review custom code or templates that may depend on specific JetEngine behavior before upgrading

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation1.0 h
  • Testing2.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,060
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,696.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-4352 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-4352 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data