CVE-2026-4662
Received Received - Intake
SQL Injection in JetEngine Plugin Allows Data Extraction

Publication date: 2026-03-24

Last updated on: 2026-03-24

Assigner: Wordfence

Description
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.
CVSS Scores
EPSS Scores
Probability:
Percentile:
Meta Information
Published
2026-03-24
Last Modified
2026-03-24
Generated
2026-05-07
AI Q&A
2026-03-24
EPSS Evaluated
2026-05-05
NVD
EUVD
Affected Vendors & Products
Showing 1 associated CPE
Vendor Product Version / Range
crocoblock jetengine to 3.8.6.1 (inc)
Helpful Resources
Exploitability
CWE
CWE Icon
KEV
KEV Icon
CWE ID Description
CWE-89 The product constructs all or part of an SQL command using externally-influenced input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could modify the intended SQL command when it is sent to a downstream component. Without sufficient removal or quoting of SQL syntax in user-controllable inputs, the generated SQL query can cause those inputs to be interpreted as SQL instead of ordinary user data.
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?

The JetEngine plugin for WordPress has a vulnerability known as SQL Injection in the `listing_load_more` AJAX action for all versions up to 3.8.6.1. This happens because the `filtered_query` parameter is not included in the HMAC signature validation, allowing attackers to bypass security checks. Additionally, the `prepare_where_clause()` method in the SQL Query Builder does not sanitize the `compare` operator before adding it to SQL statements. As a result, unauthenticated attackers can inject additional SQL queries into existing ones, potentially extracting sensitive data from the database if the site uses a JetEngine Listing Grid with Load More enabled and a SQL Query Builder query.


How can this vulnerability impact me? :

This vulnerability can allow unauthenticated attackers to extract sensitive information from your website's database by injecting malicious SQL queries. Since the attack does not require authentication, it poses a significant risk to data confidentiality. The impact is rated with a CVSS base score of 7.5, indicating a high severity with potential for data exposure but no impact on integrity or availability.


How does this vulnerability affect compliance with common standards and regulations (like GDPR, HIPAA)?:

I don't know


How can this vulnerability be detected on my network or system? Can you suggest some commands?

I don't know


What immediate steps should I take to mitigate this vulnerability?

I don't know


Ask Our AI Assistant
Need more information? Ask your question to get an AI reply (Powered by our expertise)
0/70
EPSS Chart