dbcve.org
SQL InjectionWeakness · CWE-89

CVE-2026-9065

CRITICAL · 9.3 CVSS v4.0 Published 2026-05-20
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
99/100
Remediation priority · Urgent
Remotely reachable 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
SureCart version prior to 4.2.1 are vulnerable to authenticated SQL injection via multiple parameters ('model_name', 'model_id', 'integration_id', 'provider') on the REST API endpoint '/surecart/v1/integrations/{id}'. The root cause is a flawed escaping bypass in the query builder ('wp-query-builder'). Values passed to the 'where()' method are only sanitized via '$wpdb->prepare()' when they do **not** contain a dot ('.') or the WordPress table prefix ('wp_'). By including a dot anywhere in the payload, an attacker completely bypasses the escaping logic and injects arbitrary SQL into the 'WHERE' clause, allowing full UNION-based extraction of the database.

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

SureCart versions before 4.2.1 contain an authenticated SQL injection in the REST API endpoint '/surecart/v1/integrations/{id}' via parameters including 'model_name', 'model_id', 'integration_id', and 'provider'. The vulnerability exists in the 'wp-query-builder' library where the 'where()' method only applies $wpdb->prepare() sanitization when values lack a dot ('.') or WordPress prefix ('wp_'); including a dot bypasses escaping entirely, enabling UNION-based SQL injection.

MitigationUpdate SureCart to version 4.2.1 or later. Until patched, restrict access to the REST API endpoint and monitor for suspicious patterns containing dots in parameter values.

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
High
Authentication
X
User interaction
None
Scope
X

CVSS:4.0/AV:N/AC:L/AT:N/PR:H/UI:N/VC:H/VI:H/VA:N/SC:H/SI:H/SA:H/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X

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. Confirm SureCart plugin is installed
    In WordPress admin, go to Plugins > Installed Plugins and look for SureCart. Or check the file system: look for /wp-content/plugins/surecart/ directory.
    Affected if SureCart is not installed on the WordPress site.
  2. Check installed SureCart version
    In WordPress admin, go to Plugins > Installed Plugins and find the SureCart plugin to view its version number. Alternatively, check /wp-content/plugins/surecart/surecart.php for the 'Version' header in the plugin file.
    Affected if The version number is lower than 4.2.1 (for example, 4.2.0, 4.1.x, etc.).
  3. Verify REST API access to the vulnerable endpoint
    Send an authenticated GET request to /wp-json/surecart/v1/integrations/1 using a valid WordPress user account (such as an administrator). Use a tool like curl: curl -k -u 'username:password' 'https://yourdomain.com/wp-json/surecart/v1/integrations/1'
    Affected if The API returns a valid JSON response (not a 401/403 error), indicating the endpoint is accessible to authenticated users.
  4. Check for vulnerable parameter handling
    With an authenticated session, send a request with a dot in one of the parameters (model_name, model_id, integration_id, or provider) to see if it is processed without proper escaping. For example: curl -k -u 'username:password' 'https://yourdomain.com/wp-json/surecart/v1/integrations/1?model_name=test.data'
    Affected if The parameter with a dot is processed without triggering sanitization errors or being properly escaped in the SQL query.

You are affected if SureCart is installed with a version lower than 4.2.1 AND your site allows authenticated users to access the /surecart/v1/integrations REST API endpoint.

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 SureCart to version 4.2.1 or later. Until patched, restrict access to the REST API endpoint and monitor for suspicious patterns containing dots in parameter values.

Recommended fix High confidence

SureCart version 4.2.1 or later

  1. 1. Update the SureCart plugin to version 4.2.1 or later via the WordPress admin dashboard (Plugins > SureCart > Update Now)
  2. 2. Alternatively, update via WP-CLI: `wp plugin update surecart --version=4.2.1` or `wp plugin update surecart` to get the latest version
  3. 3. Verify the update was successful by checking the plugins page or running `wp plugin get surecart`
  4. 4. Confirm the installed version is 4.2.1 or higher: `grep "Version:" /wp-content/plugins/surecart/surecart.php`
  5. 5. Test that the SQL injection vulnerability is patched by verifying the REST API endpoint '/surecart/v1/integrations/{id}' no longer accepts malicious payloads with dots in the 'model_name', 'model_id', 'integration_id', or 'provider' parameters
  6. 6. Consider running a WordPress security scan to confirm no other vulnerabilities remain
Caveat Standard WordPress plugin update best practices apply - test in staging environment first, and ensure compatibility with other plugins/theme before deploying to production

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

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,930
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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