dbcve.org
SQL InjectionWeakness · CWE-89

CVE-2026-49076

CRITICAL · 9.3 CVSS v3.1 Published 2026-06-17
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
100/100
Remediation priority · Urgent
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
Unauthenticated SQL Injection in JetEngine <= 3.8.9.1 versions.

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

An unauthenticated SQL injection vulnerability exists in the JetEngine WordPress plugin for versions 3.8.9.1 and below. Remote attackers can exploit this by sending specially crafted requests containing malicious SQL payloads to vulnerable endpoints, potentially allowing data exfiltration or database compromise.

MitigationImmediately upgrade JetEngine to a version newer than 3.8.9.1 once a patch is available, or disable the plugin if no fix is forthcoming. If immediate patching is not possible, consider restricting access to the affected endpoints at the web application firewall level.

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
Changed
Confidentiality
High
Integrity
None
Availability
Low

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

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 installation
    In WordPress admin, navigate to Plugins > Installed Plugins and locate JetEngine, or check the /wp-content/plugins/jet-engine/ directory exists on the server
    Affected if JetEngine plugin is present on the WordPress site
  2. Check installed JetEngine version
    In WordPress admin, go to Plugins > Installed Plugins > JetEngine and view the version number, or check the main plugin file header in /wp-content/plugins/jet-engine/jet-engine.php
    Affected if The displayed version is 3.8.9.1 or any version below 3.8.9.1
  3. Confirm unauthenticated endpoint exposure
    Review WordPress site configuration and any exposed REST API or AJAX endpoints related to JetEngine that may accept user input without authentication
    Affected if JetEngine endpoints that handle database queries are accessible without authentication
  4. Identify SQL injection entry points
    Examine JetEngine module settings for any features that interact with the database and are accessible to unauthenticated users, such as dynamic content, query builders, or listing components
    Affected if Features that construct database queries are enabled and accessible to unauthenticated users

If JetEngine version 3.8.9.1 or below is installed with unauthenticated-accessible database interaction features enabled, the site is likely affected by this SQL injection vulnerability.

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.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Immediately upgrade JetEngine to a version newer than 3.8.9.1 once a patch is available, or disable the plugin if no fix is forthcoming. If immediate patching is not possible, consider restricting access to the affected endpoints at the web application firewall level.

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

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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