Quick answers
- Is CVE-2026-39358 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-39358 being exploited in the wild.
- How severe is CVE-2026-39358?
- High severity, with a CVSS score of 7.2, published 13 May 2026.
- Which products and versions are affected?
- CubeCart Prior to 6.6.0.
- Is there a fix for CVE-2026-39358?
- No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.
- How is CVE-2026-39358 attacked?
- It is attacked over the network, in a network appliance.
- Am I affected by CVE-2026-39358?
- Check whether you run CubeCart at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
Technical details
An authenticated time-based blind SQL injection vulnerability exists in CubeCart v6.x before version 6.6.0. The flaw is located in the sorting parameters (sort[price], sort_activity, sort_admin, and sort_customer) within the Products and Logs administrative endpoints. The application validates that the input is an array but fails to sanitize the values within that array before passing them to the database's select method. A remote attacker with high privileges (admin access) can inject SQL payloads, such as SLEEP() commands, to extract data byte-by-byte or cause a denial of service. The issue is addressed in version 6.6.0.
Affected products
- CubeCart CubeCart v6.x Prior to 6.6.0
Timeline
- 2026-05-12: advisory: GitHub Security Advisory published
- 2026-05-13: disclosed: NVD publication date