dbcve.org
SQL InjectionWeakness · CWE-89

CVE-2026-56070

CRITICAL · 9.3 CVSS v3.1 Published 2026-06-26
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 8 weeks old

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 Advance Product Search <= 1.4.4 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 Advance Product Search plugin/component versions 1.4.4 and below. Attackers can exploit this without any authentication credentials by injecting malicious SQL queries through the product search functionality, potentially allowing unauthorized data access, modification, or in some cases, remote code execution via database compromise.

MitigationUpgrade to a version newer than 1.4.4 if available; otherwise, disable the Advance Product Search component immediately and implement web application firewall (WAF) rules or input validation as a temporary workaround until a patched version can be deployed.

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. Locate the Advance Product Search plugin version
    Access the WordPress admin dashboard under Plugins > Installed Plugins and find 'Advance Product Search' in the list. The version number is displayed below the plugin name. Alternatively, inspect the plugin's main PHP file header for the 'Version' tag, typically found in the plugin's root directory (commonly named advance-product-search.php or similar).
    Affected if The displayed version is 1.4.4 or any version number lower than 1.4.4.
  2. Confirm the plugin is active
    In the WordPress admin under Plugins > Installed Plugins, verify that the 'Advance Product Search' plugin shows as 'Active'. An inactive plugin would not be exploitable via this vulnerability.
    Affected if The plugin is currently active and the version is 1.4.4 or below.
  3. Determine if the site is publicly accessible
    Attempt to access the frontend of the WordPress site from an external network or use a browser in incognito mode to confirm the product search page is reachable without authentication. The vulnerability is exploitable by unauthenticated remote attackers.
    Affected if The product search functionality is accessible without requiring login credentials.
  4. Inspect the search parameter handling
    Review the plugin's main file(s) for SQL query construction involving the search parameter. Look for direct insertion of user input (commonly $_GET['s'], $_POST['s'], or similar request variables) into SQL statements without proper escaping or prepared statements. Use a code editor or grep to search for 'SELECT' statements containing search-related variables.
    Affected if The code contains unsanitized SQL queries that incorporate search input directly.

A user is affected if the Advance Product Search plugin is installed at version 1.4.4 or lower, is currently active, and the search functionality is accessible 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

Upgrade to a version newer than 1.4.4 if available; otherwise, disable the Advance Product Search component immediately and implement web application firewall (WAF) rules or input validation as a temporary workaround until a patched version can be deployed.

Recommended fix Moderate confidence

Version higher than 1.4.5 (check vendor for exact stable release)

  1. Upgrade Advance Product Search to a version higher than 1.4.4
  2. After upgrading, verify the SQL injection vulnerability is resolved by testing the advance product search functionality
  3. Ensure the upgrade is deployed to all affected production environments

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

Have this fixed Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,860
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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