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.

CRITICALCVE-2026-45053CVSS 9.1

CVE-2026-45053: RCE in CubeCart v6 Ecommerce Software

Plateforme

php

Composant

cubecart-v6

Corrigé dans

6.7.0

Traduction vers votre langue…

CVE-2026-45053 describes a critical Remote Code Execution (RCE) vulnerability discovered in CubeCart v6, a popular ecommerce software solution. This flaw allows authenticated attackers to upload and execute arbitrary PHP code, potentially leading to complete system takeover. The vulnerability impacts versions 6.0.0 through 6.6.9, and a patch is available in version 6.7.0.

Impact et Scénarios d'Attaquetraduction en cours…

The impact of this vulnerability is severe. An attacker with valid API credentials and the files:rw permission can leverage the REST API File Manager endpoint to upload malicious PHP files. The combination of arbitrary file upload and a path traversal vulnerability allows the attacker to write a webshell anywhere the webserver process can write, including the document root. This grants the attacker full remote code execution capabilities, enabling them to modify files, steal sensitive data (customer information, payment details, database credentials), install malware, and potentially pivot to other systems on the network. Successful exploitation could result in a complete compromise of the ecommerce platform and associated data, mirroring the impact of similar webshell vulnerabilities in other platforms.

Contexte d'Exploitationtraduction en cours…

CVE-2026-45053 was published on May 13, 2026. Its CVSS score of 9.1 (CRITICAL) reflects the high likelihood of exploitation and significant impact. Currently, there are no publicly known active campaigns targeting this vulnerability, but the availability of a straightforward exploit path makes it a likely target. The vulnerability is not listed on KEV (Known Exploited Vulnerabilities) as of this writing, but its severity warrants close monitoring. Exploitation would likely follow a similar pattern to other webshell vulnerabilities, involving the upload of a PHP webshell and subsequent use to execute commands on the server.

Renseignement sur les Menaces

Statut de l'Exploit

Preuve de ConceptInconnu
CISA KEVNO
Exposition InternetÉlevée
Rapports1 rapport de menace

Vecteur CVSS

RENSEIGNEMENT SUR LES MENACES· CVSS 3.1CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:C/C:H/I:H/A:H9.1CRITICALAttack VectorNetworkComment l'attaquant atteint la cibleAttack ComplexityLowConditions requises pour exploiterPrivileges RequiredHighNiveau d'authentification requisUser InteractionNoneSi une action de la victime est requiseScopeChangedImpact au-delà du composant affectéConfidentialityHighRisque d'exposition de données sensiblesIntegrityHighRisque de modification non autorisée de donnéesAvailabilityHighRisque 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
Modifié — l'attaque peut pivoter au-delà du composant vulnérable.
Confidentiality
Élevé — perte totale de confidentialité. L'attaquant peut lire toutes les données.
Integrity
Élevé — l'attaquant peut écrire, modifier ou supprimer toutes les données.
Availability
Élevé — panne complète ou épuisement des ressources. Déni de service total.

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

Mitigation et Contournementstraduction en cours…

The primary mitigation is to immediately upgrade CubeCart to version 6.7.0, which addresses this vulnerability. If upgrading is not immediately feasible, consider implementing temporary workarounds. Restrict API key permissions to the minimum necessary. Implement strict input validation and sanitization on the filepath parameter in the REST API File Manager endpoint. Deploy a Web Application Firewall (WAF) with rules to detect and block suspicious file uploads, particularly those containing PHP code. Monitor web server logs for unusual file creation or modification activity in the images/source/ directory. After upgrading, verify the fix by attempting to upload a test PHP file with a benign payload through the API endpoint; it should be rejected.

Comment corrigertraduction en cours…

Actualice CubeCart a la versión 6.7.0 o posterior para mitigar la vulnerabilidad de carga arbitraria de archivos. Esta actualización corrige la falla de seguridad al restringir la capacidad de subir archivos PHP maliciosos a través de la API REST.

Questions fréquentestraduction en cours…

What is CVE-2026-45053 — RCE in CubeCart v6?

CVE-2026-45053 is a critical Remote Code Execution vulnerability in CubeCart v6 ecommerce software, allowing authenticated attackers to upload and execute malicious PHP code.

Am I affected by CVE-2026-45053 in CubeCart v6?

You are affected if you are running CubeCart v6 versions 6.0.0 through 6.6.9. Upgrade to version 6.7.0 to resolve the vulnerability.

How do I fix CVE-2026-45053 in CubeCart v6?

The recommended fix is to upgrade to CubeCart version 6.7.0. Temporary workarounds include restricting API key permissions and implementing WAF rules.

Is CVE-2026-45053 being actively exploited?

While there are no currently known active campaigns, the vulnerability's severity and ease of exploitation make it a likely target. Continuous monitoring is advised.

Where can I find the official CubeCart advisory for CVE-2026-45053?

Refer to the official CubeCart security advisory on their website or GitHub repository for the most up-to-date information and patch details.

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...