CVE-2026-45054: SQL Injection in CubeCart v6
Platform
php
Component
cubecart-v6
Fixed in
6.7.0
CVE-2026-45054 describes a SQL Injection vulnerability discovered in CubeCart v6. This flaw allows an authenticated administrator to inject malicious SQL code, potentially compromising sensitive data. The vulnerability impacts versions 6.0.0 through 6.6.9 of CubeCart, and a patch is available in version 6.7.0.
Impact and Attack Scenarios
An attacker exploiting this SQL Injection vulnerability could gain unauthorized access to the CubeCart database. This could lead to the exfiltration of sensitive customer data, including personally identifiable information (PII) like names, addresses, and payment details. Furthermore, depending on the database configuration and permissions, an attacker might be able to modify or delete data, disrupt store operations, or even gain control of the underlying server. The impact is amplified by the ecommerce nature of CubeCart, which typically handles significant volumes of sensitive data. Successful exploitation could result in significant financial and reputational damage for affected businesses.
Exploitation Context
CVE-2026-45054 was published on May 13, 2026. Its severity is currently rated as MEDIUM. There are no known public exploits or active campaigns targeting this vulnerability at the time of writing. The vulnerability is not currently listed on KEV or EPSS, suggesting a low probability of immediate exploitation. Refer to the official CubeCart advisory for further details.
Threat Intelligence
Exploit Status
CISA SSVC
CVSS Vector
What do these metrics mean?
- Attack Vector
- Network — remotely exploitable over the internet. No physical or local access required. Widest attack surface.
- Attack Complexity
- Low — no special conditions required. Attacker can exploit reliably without depending on rare configurations or timing.
- Privileges Required
- High — admin or privileged account required to exploit.
- User Interaction
- None — attack is automatic and silent. Victim does nothing: no click, no file open.
- Scope
- Unchanged — impact is limited to the vulnerable component itself.
- Confidentiality
- High — complete confidentiality loss. Attacker can read all data: credentials, keys, personal data.
- Integrity
- None — no integrity impact. Attacker cannot modify data.
- Availability
- None — no availability impact. Service remains fully operational.
Affected Software
Weakness Classification (CWE)
Timeline
- Reserved
- Published
- Modified
Mitigation and Workarounds
The primary mitigation for CVE-2026-45054 is to upgrade CubeCart to version 6.7.0 or later, which contains the necessary fix. If an immediate upgrade is not possible, consider implementing a Web Application Firewall (WAF) rule to filter potentially malicious SQL fragments in the sort parameter of the admin.php?_g=orders&node=transactions endpoint. Specifically, look for unusual characters or SQL keywords within the sort parameter. Additionally, review and restrict database user permissions to limit the potential impact of a successful SQL Injection attack. After upgrading, confirm the vulnerability is resolved by attempting a SQL Injection payload in the affected endpoint and verifying that it is properly sanitized.
How to fix
Actualice CubeCart a la versión 6.7.0 o posterior para mitigar la vulnerabilidad de inyección SQL. Esta actualización corrige la falta de validación en el parámetro 'sort[]', previniendo la ejecución de código SQL malicioso por parte de administradores autenticados.
Frequently asked questions
What is CVE-2026-45054 — SQL Injection in CubeCart v6?
CVE-2026-45054 is a SQL Injection vulnerability affecting CubeCart v6 versions 6.0.0 through 6.6.9. It allows an authenticated admin to inject malicious SQL code, potentially compromising sensitive data.
Am I affected by CVE-2026-45054 in CubeCart v6?
You are affected if you are running CubeCart v6 versions 6.0.0 through 6.6.9 and have not yet upgraded to version 6.7.0 or later.
How do I fix CVE-2026-45054 in CubeCart v6?
The recommended fix is to upgrade CubeCart to version 6.7.0 or later. As a temporary workaround, implement a WAF rule to filter malicious SQL fragments in the sort parameter.
Is CVE-2026-45054 being actively exploited?
As of the current date, there are no known public exploits or active campaigns targeting CVE-2026-45054.
Where can I find the official CubeCart advisory for CVE-2026-45054?
Please refer to the official CubeCart security advisory for detailed information and updates regarding CVE-2026-45054. Check the CubeCart website or security mailing lists for the latest advisory.
Is your project affected?
Upload your dependency file and we'll tell you instantly if this and other CVEs hit you.
Try it now — no account
Upload any manifest (composer.lock, package-lock.json, WordPress plugin list…) or paste your component list. You get a vulnerability report instantly. Uploading a file is just the start: with an account you get continuous monitoring, Slack/email alerts, multi-project and white-label reports.
Drag & drop your dependency file
composer.lock, package-lock.json, requirements.txt, Gemfile.lock, pubspec.lock, Dockerfile...