CVE-2026-9065: Surecart - SQL Injection
SureCart version prior to 4.2.1 are vulnerable to authenticated SQL injection via multiple parameters ('modelname', 'modelid', 'integrationid', '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.
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade
SureCartto a version that resolves this vulnerability.Fixed in 4.2.1 - Compensating control
Mitigate by preventing authenticated access to the vulnerable REST API endpoint '/surecart/v1/integrations/{id}' from untrusted users/systems until the SureCart upgrade to 4.2.1 is completed.
Event History
Frequently Asked Questions
What is the severity of CVE-2026-9065?
CVE-2026-9065 is considered a high severity vulnerability due to its potential to allow attackers to exploit authenticated SQL injection.
How do I fix CVE-2026-9065?
To mitigate CVE-2026-9065, upgrade SureCart to version 4.2.1 or later, where this vulnerability has been resolved.
What components of SureCart are affected by CVE-2026-9065?
CVE-2026-9065 affects SureCart versions prior to 4.2.1 on multiple parameters including 'model_name', 'model_id', 'integration_id', and 'provider'.
What is the nature of the vulnerability in CVE-2026-9065?
The vulnerability in CVE-2026-9065 is an authenticated SQL injection that arises from improper escaping mechanisms in the REST API.
Does CVE-2026-9065 require authentication for exploitation?
Yes, CVE-2026-9065 requires authentication to exploit the SQL injection vulnerability on the affected REST API endpoint.