dbcve.org
SQL InjectionWeakness · CWE-89

CVE-2025-49931

CRITICAL · 9.3 CVSS v3.1 Published 2025-10-22
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
Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection') vulnerability in Crocoblock JetSearch jet-search allows Blind SQL Injection.This issue affects JetSearch: from n/a through <= 3.5.10.

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 · moderate confidence

A blind SQL injection vulnerability exists in the Crocoblock JetSearch plugin (jet-search) due to improper neutralization of special elements in SQL commands. This allows attackers to inject malicious SQL queries through unsanitized input parameters in JetSearch functionality.

MitigationUpdate JetSearch to a version newer than 3.5.10 when a patch is released. If no patch is available, disable the plugin or implement web application firewall rules to block malicious SQL injection payloads on affected endpoints.

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. Identify if JetSearch plugin is installed
    Check the WordPress plugins directory (/wp-content/plugins/) for a folder named 'jet-search' or inspect the plugin list via WordPress admin under Plugins > Installed Plugins
    Affected if The jet-search plugin folder exists in the WordPress plugins directory
  2. Determine installed JetSearch version
    Open the main plugin file (usually jet-search.php) and locate the 'Version' header comment in the plugin metadata, or check via WordPress admin plugin list
    Affected if The installed version is 3.5.10 or lower (the version before the patch is applied)
  3. Verify if plugin is active on the site
    Check WordPress admin > Plugins > Installed Plugins to confirm JetSearch status shows 'Active', or query the wp_options table for option_name 'active_plugins'
    Affected if The plugin is enabled and active on the WordPress site
  4. Confirm JetSearch search functionality is in use
    Check pages/posts/widgets for JetSearch search widgets or shortcodes (such as [jet_search] or [jet_search_form]), or inspect frontend for search input elements powered by JetSearch
    Affected if Any JetSearch search form or widget is published and accessible on the site

The environment is affected if the JetSearch plugin is installed, active, and exposes search functionality, with an unpatched version at or below the vulnerable range.

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

Update JetSearch to a version newer than 3.5.10 when a patch is released. If no patch is available, disable the plugin or implement web application firewall rules to block malicious SQL injection payloads on affected endpoints.

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

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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