Quick answers
- Is CVE-2026-45708 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-45708 being exploited in the wild.
- How severe is CVE-2026-45708?
- High severity, with a CVSS score of 7.2, published 13 May 2026.
- Which products and versions are affected?
- CubeCart < 6.7.3.
- Is there a fix for CVE-2026-45708?
- A patch was published on 2026-05-13: Fixed in version 6.7.3 Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-45708 attacked?
- It is attacked over the network, in a web application.
- Am I affected by CVE-2026-45708?
- Check whether you run CubeCart at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
Technical details
A code injection vulnerability exists in CubeCart's Invoice Editor (admin/sources/documents.invoice.inc.php) where the application reads from $GLOBALS['RAW']['POST']['content'], bypassing global HTML sanitization. While Smarty security policies are in place, they do not filter raw PHP tags (<?php ... ?>). When an administrator prints an order, the rendered template—including the raw PHP—is written to a file named 'print.<md5>.php' in the /files/ directory. Due to an explicit 'allow from all' directive in the files/.htaccess for print.*.php files, these files become publicly accessible. An attacker can then execute arbitrary code with the privileges of the web server user. This is fixed in version 6.7.3 by stripping PHP tags before writing the print artifact.
Affected products
- CubeCart CubeCart < 6.7.3
Timeline
- 2026-05-12: advisory: GitHub Security Advisory published
- 2026-05-13: disclosed: NVD publication date
- 2026-05-13: patched: Fixed in version 6.7.3