dbcve.org
SQL InjectionWeakness · CWE-89

CVE-2026-49079

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 JetSearch <= 3.5.17 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

Unauthenticated SQL Injection vulnerability in JetSearch plugin versions 3.5.17 and below allows remote attackers to inject arbitrary SQL queries via unsanitized input parameters, potentially leading to data exfiltration or complete database compromise.

MitigationUpdate JetSearch to a version newer than 3.5.17. If no patched version is available, disable the plugin until a fix is released.

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 JetSearch plugin installation
    Check WordPress plugins directory for jet-search folder, or view installed plugins in WordPress admin under Plugins > Installed Plugins
    Affected if JetSearch plugin is found in the WordPress installation
  2. Check installed JetSearch version
    View the plugin version in WordPress admin (Plugins > Installed Plugins > JetSearch) or read version from plugin main file at wp-content/plugins/jet-search/readme.txt or primary PHP file
    Affected if Version is 3.5.17 or lower
  3. Determine if search functionality is publicly accessible
    Identify if JetSearch widget or shortcode is deployed on public-facing pages; test if search endpoint responds to unauthenticated requests
    Affected if Search feature is accessible without requiring authentication
  4. Inspect logs for SQL injection indicators
    Review web server access logs and database query logs for suspicious patterns such as UNION SELECT, OR 1=1, or other SQL syntax in search-related parameters
    Affected if Unusual SQL syntax detected in logs related to JetSearch endpoints

Environment is affected if JetSearch plugin version 3.5.17 or earlier is installed AND the search functionality is exposed to unauthenticated users

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 JetSearch to a version newer than 3.5.17. If no patched version is available, disable the plugin until a fix is released.

Recommended fix Moderate confidence

JetSearch 3.5.18 or latest available version (upgrade from <= 3.5.17)

  1. 1. Backup your WordPress site and database before performing any updates
  2. 2. Navigate to WordPress admin dashboard > Plugins
  3. 3. Locate JetSearch plugin in the installed plugins list
  4. 4. Check if an update is available for JetSearch
  5. 5. If update available, click 'Update Now' to install the latest version
  6. 6. Alternatively, download the latest version from WordPress.org or your purchase source and upload via Plugins > Add New > Upload Plugin
  7. 7. Verify the update completed successfully by checking the plugin version number
Caveat Review plugin settings and any custom integrations after upgrade to ensure compatibility

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

Have this fixed Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing4.0 h
  • Review / QA3.0 h
16.0 hours of engineering $2,820
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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