dbcve.org
SQL InjectionWeakness · CWE-89

CVE-2026-39358

HIGH · 7.2 CVSS v3.1 Published 2026-05-13
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
78/100
Remediation priority · High
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
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.

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

Authenticated time-based blind SQL injection vulnerability in CubeCart v6.x affecting sorting parameters (sort[price], sort_activity, sort_admin, sort_customer) in Products and Logs endpoints. An authenticated attacker can inject malicious SQL commands through these parameters to compromise database confidentiality and integrity.

MitigationUpgrade to CubeCart version 6.6.0 or later, which contains the fix for this SQL injection vulnerability.

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
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H

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. Locate CubeCart installation version
    Check the version file (commonly includes version number in a PHP file like /includes/version.php or in the admin dashboard footer) or access the admin panel and look at the footer or 'About' section
    Affected if The installed version is CubeCart v6.x below version 6.6.0
  2. Confirm admin access to Products endpoint
    Log into the CubeCart admin panel and navigate to the Products section (typically /admin.php?_g=products or similar), then inspect whether the sorting functionality is present
    Affected if The Products endpoint is accessible and sorting parameters (such as sort[price]) are functional
  3. Confirm admin access to Logs endpoint
    Log into the CubeCart admin panel and navigate to the System Logs or Logs section (typically /admin.php?_g=logs or similar), then inspect whether sorting parameters are available
    Affected if The Logs endpoint is accessible and sorting parameters (such as sort_activity, sort_admin, sort_customer) are functional

You are affected if running CubeCart version 6.x below 6.6.0 AND you have authenticated admin access to the Products or Logs endpoints where sorting parameters are used.

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

Upgrade to CubeCart version 6.6.0 or later, which contains the fix for this SQL injection vulnerability.

Recommended fix Moderate confidence

CubeCart 6.6.0

  1. 1. Backup your existing CubeCart installation and database before proceeding with any upgrade.
  2. 2. Download CubeCart version 6.6.0 from the official source (official CubeCart website or verified repository).
  3. 3. Replace the existing CubeCart files with the new version 6.6.0 files, preserving your configuration and custom assets as per upgrade documentation.
  4. 4. Run any provided database migration scripts included in the 6.6.0 release.
  5. 5. Verify the upgrade was successful by logging into the admin panel.
  6. 6. Test the Products and Logs endpoints with sorting parameters (sort[price], sort_activity, sort_admin, sort_customer) to confirm the SQL injection vulnerability is no longer present.
  7. 7. Monitor application logs for any unusual database activity.

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

Have this fixed Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,490
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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