此页面尚未翻译为您的语言。我们正在努力翻译，目前显示英文内容。
💡 Keep dependencies up to date — most exploits target known, patchable vulnerabilities.
CVE-2026-45708: RCE in CubeCart v6 Ecommerce Software
翻译中…平台
php
组件
cubecart-v6
修复版本
6.7.3
CVE-2026-45708 is a Remote Code Execution (RCE) vulnerability affecting CubeCart v6 ecommerce software. An attacker with administrative privileges and document editing permissions can inject malicious PHP code into the Invoice Editor. This code is then executed when any administrator attempts to print an order, allowing for arbitrary code execution on the server. The vulnerability impacts CubeCart versions 6.0.0 through 6.7.2 and is resolved in version 6.7.3.
影响与攻击场景翻译中…
Successful exploitation of CVE-2026-45708 allows an attacker to execute arbitrary code on the CubeCart server with the privileges of the web server user. This could lead to complete compromise of the system, including data theft, modification, and deletion. The attacker could potentially gain access to sensitive customer data, payment information, and other confidential business information. Given the ecommerce nature of CubeCart, the blast radius extends to all customers and partners interacting with the affected site. The vulnerability's reliance on a print function and .htaccess carve-out makes it relatively easy to trigger, increasing the risk of exploitation.
利用背景翻译中…
CVE-2026-45708 was published on May 13, 2026. Its severity is rated as HIGH with a CVSS score of 7.2. There is currently no indication of active exploitation campaigns targeting this vulnerability. Public proof-of-concept (POC) code is likely to emerge given the vulnerability's relatively straightforward exploitation path. The vulnerability is not currently listed on CISA Known Exploited Vulnerabilities (KEV) catalog.
威胁情报
漏洞利用状态
CVSS 向量
这些指标意味着什么？
- Attack Vector
- 网络 — 可通过互联网远程利用，无需物理或本地访问。攻击面最大。
- Attack Complexity
- 低 — 无需特殊条件，可以稳定地利用漏洞。
- Privileges Required
- 高 — 需要管理员或特权账户。
- User Interaction
- 无 — 攻击自动且无声，受害者无需任何操作。
- Scope
- 未改变 — 影响仅限于脆弱组件本身。
- Confidentiality
- 高 — 完全丧失机密性，攻击者可读取所有数据。
- Integrity
- 高 — 攻击者可写入、修改或删除任何数据。
- Availability
- 高 — 完全崩溃或资源耗尽，完全拒绝服务。
受影响的软件
弱点分类 (CWE)
时间线
- 已保留
- 发布日期
缓解措施和替代方案翻译中…
The primary mitigation for CVE-2026-45708 is to immediately upgrade CubeCart to version 6.7.3 or later. If upgrading is not immediately feasible, a temporary workaround involves restricting file access permissions for the files/print.*.php directory. Specifically, ensure that the web server user does not have write access to this directory. Additionally, consider implementing a Web Application Firewall (WAF) rule to block requests containing suspicious PHP code in the Invoice Editor. After upgrading, confirm the fix by attempting to print an order and verifying that no malicious code is executed.
修复方法翻译中…
Actualice CubeCart a la versión 6.7.3 o posterior para mitigar esta vulnerabilidad. La actualización corrige la forma en que se manejan las plantillas de factura, evitando la ejecución remota de código no autorizada.
常见问题翻译中…
What is CVE-2026-45708 — RCE in CubeCart v6?
CVE-2026-45708 is a Remote Code Execution vulnerability in CubeCart v6 ecommerce software. It allows an admin to inject malicious PHP code, leading to code execution when an order is printed. The CVSS score is 7.2 (HIGH).
Am I affected by CVE-2026-45708 in CubeCart v6?
You are affected if you are running CubeCart v6 versions 6.0.0 through 6.7.2. If you are using a later version, you are not vulnerable.
How do I fix CVE-2026-45708 in CubeCart v6?
Upgrade CubeCart to version 6.7.3 or later. As a temporary workaround, restrict file access permissions for the files/print.*.php directory.
Is CVE-2026-45708 being actively exploited?
There is currently no indication of active exploitation campaigns targeting CVE-2026-45708, but public POC code is likely to emerge.
Where can I find the official CubeCart advisory for CVE-2026-45708?
Refer to the official CubeCart security advisory on their website for detailed information and updates regarding CVE-2026-45708.
立即试用 — 无需账户
上传任何清单文件 (composer.lock, package-lock.json, WordPress 插件列表…) 或粘贴您的组件列表。您立即获得一份漏洞报告。上传文件只是开始：拥有账户后，您将获得持续监控、Slack/电子邮件警报、多项目和白标报告。
拖放您的依赖文件
composer.lock、package-lock.json、requirements.txt、Gemfile.lock、pubspec.lock、Dockerfile...