CVE-2026-39428: XSS in CubeCart 6.0.0 - 6.6.0
Platform
php
Component
cubecart
Fixed in
6.6.0
A Stored Cross-Site Scripting (XSS) vulnerability has been identified in CubeCart versions 6.0.0 through 6.5.9. This vulnerability allows an attacker with administrative privileges to inject malicious JavaScript payloads into various product fields. These payloads are then stored in the database and executed when users, including other administrators, view the affected product pages, potentially leading to session hijacking or unauthorized actions. The vulnerability is resolved in CubeCart version 6.6.0.
Impact and Attack Scenarios
Successful exploitation of CVE-2026-39428 allows an attacker to inject arbitrary JavaScript code into CubeCart product pages. This code executes in the context of the user viewing the page, enabling the attacker to steal session cookies, redirect users to malicious websites, or perform actions on behalf of the user, including modifying product information or accessing sensitive data. The impact is particularly severe for administrators, as an attacker could gain full control over the CubeCart installation. This vulnerability shares similarities with other XSS vulnerabilities where user input is not properly sanitized before being stored and displayed, potentially leading to account takeover and data breaches.
Exploitation Context
CVE-2026-39428 was published on May 13, 2026. Its severity is rated as Medium. No public proof-of-concept (POC) code has been publicly released at the time of writing. There are no indications of active exploitation campaigns targeting this vulnerability. This CVE is not currently listed on the CISA Known Exploited Vulnerabilities (KEV) catalog.
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
- Required — victim must take an action: open a file, click a link, or visit a crafted page.
- Scope
- Changed — successful attack can pivot beyond the vulnerable component to other systems or the host OS.
- Confidentiality
- Low — partial or indirect data access. Attacker gains limited information.
- Integrity
- Low — attacker can modify some data with limited scope or impact.
- 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-39428 is to upgrade CubeCart to version 6.6.0 or later, which contains the fix. If immediate upgrading is not possible, consider implementing stricter input validation and output encoding on all user-supplied data within CubeCart. While not a complete solution, a Web Application Firewall (WAF) configured to detect and block XSS payloads targeting product fields can provide an additional layer of defense. Regularly review and audit CubeCart configurations to ensure best practices are followed.
How to fix
Actualice CubeCart a la versión 6.6.0 o posterior para mitigar la vulnerabilidad de XSS. Esta actualización corrige la forma en que se almacenan y procesan los datos de los productos, evitando la inyección de código malicioso. Asegúrese de realizar una copia de seguridad de su base de datos antes de actualizar.
Frequently asked questions
What is CVE-2026-39428 — XSS in CubeCart?
CVE-2026-39428 is a Stored Cross-Site Scripting (XSS) vulnerability affecting CubeCart versions 6.0.0 through 6.5.9. It allows attackers with admin privileges to inject malicious JavaScript into product pages.
Am I affected by CVE-2026-39428 in CubeCart?
You are affected if you are running CubeCart version 6.0.0 through 6.5.9 and have not yet upgraded to version 6.6.0 or later. Check your CubeCart version to determine your exposure.
How do I fix CVE-2026-39428 in CubeCart?
The recommended fix is to upgrade CubeCart to version 6.6.0 or later. This version includes a patch that addresses the XSS vulnerability.
Is CVE-2026-39428 being actively exploited?
There are currently no indications of active exploitation campaigns targeting CVE-2026-39428, but it's crucial to apply the patch to prevent potential future attacks.
Where can I find the official CubeCart advisory for CVE-2026-39428?
Refer to the official CubeCart security advisory for detailed information and updates regarding CVE-2026-39428: [https://www.cubecart.com/security/](https://www.cubecart.com/security/)
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...