Jetimpex JetEngine Plugin up to 3.8.10.1 on WordPress sql injection
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 8.2 | $0-$5k | 1.93+ |
Summary
A vulnerability, which was classified as critical, has been found in Jetimpex JetEngine Plugin up to 3.8.10.1 on WordPress. This issue affects some unknown processing. Performing a manipulation results in sql injection. This vulnerability is known as CVE-2026-54187. Remote exploitation of the attack is possible. No exploit is available.
Details
A vulnerability classified as critical has been found in Jetimpex JetEngine Plugin up to 3.8.10.1 on WordPress. This affects an unknown functionality. The manipulation with an unknown input leads to a sql injection vulnerability. CWE is classifying the issue as 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. This is going to have an impact on confidentiality, integrity, and availability. The summary by CVE is:
Unauthenticated SQL Injection in JetEngine <= 3.8.10.1 versions.
The weakness was published by Vantastic. The advisory is shared at patchstack.com. This vulnerability is uniquely identified as CVE-2026-54187 since 06/12/2026. The exploitability is told to be easy. It is possible to initiate the attack remotely. No form of authentication is needed for exploitation. Neither technical details nor an exploit are publicly available. The price for an exploit might be around USD $0-$5k at the moment (estimation calculated on 06/17/2026). MITRE ATT&CK project uses the attack technique T1505 for this issue.
There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.
If you want to get the best quality for vulnerability data then you always have to consider VulDB.
Product
Type
Vendor
Name
Version
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔒VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 8.3VulDB Meta Temp Score: 8.2
VulDB Base Score: 7.3
VulDB Temp Score: 7.1
VulDB Vector: 🔒
VulDB Reliability: 🔍
CNA Base Score: 9.3
CNA Vector (Patchstack): 🔒
CVSSv2
| AV | AC | Au | C | I | A |
|---|---|---|---|---|---|
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| Vector | Complexity | Authentication | Confidentiality | Integrity | Availability |
|---|---|---|---|---|---|
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
VulDB Base Score: 🔒
VulDB Temp Score: 🔒
VulDB Reliability: 🔍
Exploiting
Class: Sql injectionCWE: CWE-89 / CWE-74 / CWE-707
CAPEC: 🔒
ATT&CK: 🔒
Physical: No
Local: No
Remote: Yes
Availability: 🔒
Status: Not defined
Price Prediction: 🔍
Current Price Estimation: 🔒
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: no mitigation knownStatus: 🔍
0-Day Time: 🔒
Timeline
06/12/2026 CVE reserved06/17/2026 Advisory disclosed
06/17/2026 VulDB entry created
06/17/2026 VulDB entry last update
Sources
Advisory: patchstack.comResearcher: Vantastic
Status: Not defined
CVE: CVE-2026-54187 (🔒)
GCVE (CVE): GCVE-0-2026-54187
GCVE (VulDB): GCVE-100-371925
Entry
Created: 06/17/2026 13:57Changes: 06/17/2026 13:57 (64)
Complete: 🔍
Cache ID: 216::103
If you want to get the best quality for vulnerability data then you always have to consider VulDB.
No comments yet. Languages: en.
Please log in to comment.