Code Injection in CubeCart (CVE-2026-45708)
Summary
Code injection in CubeCart (CVE-2026-45708). Successful exploitation can lead to full system takeover. Mitigation: upgrade to 6.7.3 or later.
Original description
The description as published by the source.
CubeCart is an ecommerce software solution. Prior to 6.7.3, an admin with documents edit permission can save raw <?php … ?> into the Invoice Editor. The next time any admin clicks Print on any order, the rendered template is written to files/print..php. files/.htaccess ships an explicit allow from all carve-out, so the file is fetched and executed by any unauthenticated visitor. This vulnerability is fixed in 6.7.3.
Source: NIST National Vulnerability Database NVD GitHub Advisory
Auto-generated summary
Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.
A vulnerability tracked as CVE-2026-45708 has been found in CubeCart.
Successful exploitation can lead to full system takeover. CVSS score: 7.2/10.
What to do: upgrade CubeCart to 6.7.3 or later.
If unsure, ask your IT team or search "CubeCart CVE-2026-45708" on the vendor's site.
CVE-2026-45708 (CubeCart) — CWE-94 / CVSS v3 7.2
Attack vector: remote (network-reachable) / no user interaction
Patched: 6.7.3 — apply immediately
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
Arbitrary code execution (CWE-94) exists in CubeCart.
Check the vendor advisory for the affected versions of CubeCart.
Severity: High (CVSS 7.2/10). Successful exploitation can lead to full system takeover.
Update to 6.7.3.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r 'CubeCart' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.
Response actions
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
grep -r 'CubeCart' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
CubeCartを grep し、稼働しているサービス・バージョンを把握する。 -
2Apply patch patch
Upgrade CubeCart to 6.7.3ステージング環境で 6.7.3 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
3Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
References
- advisory github.com
- advisory github.com
- advisory nvd.nist.gov