GHSA-QP65-J7F9-QV73
Vulnerability from github – Published: 2026-05-20 09:30 – Updated: 2026-05-20 09:30SureCart 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.
{
"affected": [],
"aliases": [
"CVE-2026-9065"
],
"database_specific": {
"cwe_ids": [
"CWE-89"
],
"github_reviewed": false,
"github_reviewed_at": null,
"nvd_published_at": "2026-05-20T09:16:27Z",
"severity": "CRITICAL"
},
"details": "SureCart version prior to 4.2.1 are vulnerable to authenticated SQL injection via multiple parameters (\u0027model_name\u0027, \u0027model_id\u0027, \u0027integration_id\u0027, \u0027provider\u0027) on the REST API endpoint \u0027/surecart/v1/integrations/{id}\u0027.\n\nThe root cause is a flawed escaping bypass in the query builder (\u0027wp-query-builder\u0027). Values passed to the \u0027where()\u0027 method are only sanitized via \u0027$wpdb-\u003eprepare()\u0027 when they do **not** contain a dot (\u0027.\u0027) or the WordPress table prefix (\u0027wp_\u0027). By including a dot anywhere in the payload, an attacker completely bypasses the escaping logic and injects arbitrary SQL into the \u0027WHERE\u0027 clause, allowing full UNION-based extraction of the database.",
"id": "GHSA-qp65-j7f9-qv73",
"modified": "2026-05-20T09:30:34Z",
"published": "2026-05-20T09:30:34Z",
"references": [
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2026-9065"
},
{
"type": "WEB",
"url": "https://www.tenable.com/security/research/tra-2026-43"
}
],
"schema_version": "1.4.0",
"severity": [
{
"score": "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",
"type": "CVSS_V4"
}
]
}
Sightings
| Author | Source | Type | Date | Other |
|---|
Nomenclature
- Seen: The vulnerability was mentioned, discussed, or observed by the user.
- Confirmed: The vulnerability has been validated from an analyst's perspective.
- Published Proof of Concept: A public proof of concept is available for this vulnerability.
- Exploited: The vulnerability was observed as exploited by the user who reported the sighting.
- Patched: The vulnerability was observed as successfully patched by the user who reported the sighting.
- Not exploited: The vulnerability was not observed as exploited by the user who reported the sighting.
- Not confirmed: The user expressed doubt about the validity of the vulnerability.
- Not patched: The vulnerability was not observed as successfully patched by the user who reported the sighting.
The approach is described in our paper Mapping CVEs to MITRE ATT&CK Techniques: A Curated Gold-Set Classifier and the Limits of LLM-Assisted Label Expansion.
Browse all ATT&CK techniques and the vulnerabilities related to each.
Related by attack behaviour
Vulnerabilities whose description is nearest to this one in the vector space of the CIRCL/vulnerability-attack-technique-biencoder model. This is a similarity search over the bi-encoder space (plain cosine), not a classification, and it has no measured accuracy.