# CVE-2026-39358: CubeCart: Time-based Blind SQL Injection

> Authenticated attackers can execute arbitrary SQL commands via sorting parameters in CubeCart, compromising database confidentiality and integrity.

- **Severity:** High 7.2 (`CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 13 May 2026
- **Updated:** 14 May 2026
- **Also known as:** GHSA-8gj6-9fwc-h4gh

## What is CVE-2026-39358?

CVE-2026-39358 is a high-severity SQL injection vulnerability in cubecart v6, published on 13 May 2026. An attacker needs administrator access to exploit it, with no action from the victim.

### Official description

CubeCart is an ecommerce software solution. Prior to 6.6.0, Authenticated Time-Based Blind SQL Injection vulnerabilities were identified in the sorting parameters (sort[price], sort_activity, sort_admin, and sort_customer) of the Products and Logs endpoints in CubeCart v6.x. This allows an attacker to execute arbitrary SQL commands, compromising the confidentiality and integrity of the database. This vulnerability is fixed in 6.6.0.

Weakness: CWE-89 (Improper Neutralization of Special Elements used in an SQL Command)

## Which versions are affected by CVE-2026-39358?


## How do I fix CVE-2026-39358?

No fix has been published for CVE-2026-39358 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-39358 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-39358 exists.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-39358 and fix it if it is affected.

What it is: CVE-2026-39358 is a high-severity SQL injection vulnerability in cubecart v6, published on 13 May 2026. An attacker needs administrator access to exploit it, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-39358 exists.

Affected product: cubecart v6. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-39358/ (Markdown: https://insights.sbomify.com/CVE-2026-39358/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-39358
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-39358
- OSV: https://osv.dev/vulnerability/CVE-2026-39358

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-39358/
Summaries are generated and may contain mistakes; the official description above is the record.