Cette page n'a pas encore été traduite dans votre langue. Affichage du contenu en anglais pendant que nous y travaillons.

💡 Keep dependencies up to date — most exploits target known, patchable vulnerabilities.

MEDIUMCVE-2026-45054CVSS 4.9

CVE-2026-45054: SQL Injection in CubeCart v6

Plateforme

php

Composant

cubecart-v6

Corrigé dans

6.7.0

Traduction vers votre langue…

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 et Scénarios d'Attaquetraduction en cours…

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.

Contexte d'Exploitationtraduction en cours…

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.

Renseignement sur les Menaces

Statut de l'Exploit

Preuve de ConceptInconnu
CISA KEVNO
Exposition InternetÉlevée

CISA SSVC

Exploitationpoc
Automatisableno
Impact Techniquepartial

Vecteur CVSS

RENSEIGNEMENT SUR LES MENACES· CVSS 3.1CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:N/A:N4.9MEDIUMAttack VectorNetworkComment l'attaquant atteint la cibleAttack ComplexityLowConditions requises pour exploiterPrivileges RequiredHighNiveau d'authentification requisUser InteractionNoneSi une action de la victime est requiseScopeUnchangedImpact au-delà du composant affectéConfidentialityHighRisque d'exposition de données sensiblesIntegrityNoneRisque de modification non autorisée de donnéesAvailabilityNoneRisque d'interruption de servicenextguardhq.com · Score de base CVSS v3.1
Que signifient ces métriques?
Attack Vector
Réseau — exploitable à distance via internet. Aucun accès physique ou local requis.
Attack Complexity
Faible — aucune condition spéciale requise. Exploitable de manière fiable.
Privileges Required
Élevé — un compte administrateur ou privilégié est requis.
User Interaction
Aucune — attaque automatique et silencieuse. La victime ne fait rien.
Scope
Inchangé — impact limité au composant vulnérable.
Confidentiality
Élevé — perte totale de confidentialité. L'attaquant peut lire toutes les données.
Integrity
Aucun — aucun impact sur l'intégrité.
Availability
Aucun — aucun impact sur la disponibilité.

Logiciel Affecté

Composantcubecart-v6
Fournisseurcubecart
Version minimale6.0.0
Version maximale< 6.7.0
Corrigé dans6.7.0

Classification de Faiblesse (CWE)

Chronologie

  1. Réservé
  2. Publiée
  3. Modifiée

Mitigation et Contournementstraduction en cours…

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.

Comment corrigertraduction en cours…

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.

Questions fréquentestraduction en cours…

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.

Ton projet est-il affecté ?

Téléverse ton fichier de dépendances et découvre instantanément si cette CVE et d'autres te touchent.

en directfree scan

Essayez maintenant — sans compte

scanZone.subtitle

Scan manuelSlack/email alertsContinuous monitoringWhite-label reports

Glissez-déposez votre fichier de dépendances

composer.lock, package-lock.json, requirements.txt, Gemfile.lock, pubspec.lock, Dockerfile...