dbcve.org
SQL InjectionWeakness · CWE-89

CVE-2026-4662

HIGH · 7.5 CVSS v3.1 Published 2026-03-24
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 `listing_load_more` AJAX action in all versions up to, and including, 3.8.6.1. This is due to the `filtered_query` parameter being excluded from the HMAC signature validation (allowing attacker-controlled input to bypass security checks) combined with the `prepare_where_clause()` method in the SQL Query Builder not sanitizing the `compare` operator before concatenating it into SQL statements. 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, provided the site has a JetEngine Listing Grid with Load More enabled that uses a SQL Query Builder query.

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 WordPress plugin versions up to 3.8.6.1 contain an unauthenticated SQL injection vulnerability in the `listing_load_more` AJAX action. Attackers can exploit this because the `filtered_query` parameter bypasses HMAC signature validation, and the `prepare_where_clause()` method fails to sanitize the `compare` operator before SQL concatenation. Successful exploitation requires the target site to have a JetEngine Listing Grid with Load More enabled using a SQL Query Builder query.

MitigationUpdate JetEngine to the latest version immediately. If immediate updating is not feasible, disable the Load More feature on Listing Grids that use the SQL Query Builder, as this removes the attack vector.

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. Verify JetEngine plugin version
    Check the installed JetEngine plugin version in WordPress admin under Plugins, or inspect the plugin header in the main plugin file
    Affected if The installed version is 3.8.6.1 or lower
  2. Confirm listing_load_more AJAX endpoint is accessible
    Verify the AJAX action 'listing_load_more' is available to unauthenticated users by inspecting WordPress AJAX hooks or testing the endpoint
    Affected if The AJAX action accepts requests from unauthenticated (logged-out) users
  3. Identify Listing Grids with Load More enabled
    Review all JetEngine Listing Grid widgets/elements on the site and check their settings for the Load More feature
    Affected if Any Listing Grid has Load More functionality enabled in its configuration
  4. Check if Load More grids use SQL Query Builder
    For each Listing Grid with Load More enabled, inspect the query source settings to determine if SQL Query Builder is being used
    Affected if Any Listing Grid with Load More uses a query built with the SQL Query Builder rather than a standard post/query source

A site is affected if it runs JetEngine 3.8.6.1 or lower, has the listing_load_more AJAX action exposed to unauthenticated users, and uses a Listing Grid with both Load More enabled and a SQL Query Builder query.

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 the latest version immediately. If immediate updating is not feasible, disable the Load More feature on Listing Grids that use the SQL Query Builder, as this removes the attack vector.

Recommended fix High confidence

JetEngine version 3.8.7 or later

  1. Log in to the WordPress admin dashboard
  2. Navigate to Plugins > Installed Plugins
  3. Find JetEngine in the plugin list
  4. If an update is available, click 'Update Now' to update to the latest version, which includes the fix for this vulnerability
  5. Alternatively, you can upload the updated JetEngine plugin zip file from crocoblock.com if auto-update is not available
  6. After updating, verify the JetEngine version is 3.8.7 or later in Plugins > Installed Plugins

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

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation3.0 h
  • Testing4.0 h
  • Review / QA1.0 h
10.0 hours of engineering $1,720
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-4662 — 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-4662 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