Quick answers
- Is CVE-2026-44377 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-44377 being exploited in the wild.
- How severe is CVE-2026-44377?
- Critical severity, with a CVSS score of 9.1, published 13 May 2026.
- Which products and versions are affected?
- CubeCart < 6.7.0.
- Is there a fix for CVE-2026-44377?
- No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.
- How is CVE-2026-44377 attacked?
- It is attacked over the network, in a network appliance.
- Am I affected by CVE-2026-44377?
- 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
An Authenticated Server-Side Template Injection (SSTI) vulnerability exists in CubeCart versions prior to 6.7.0 due to an incomplete Smarty Security Policy. While common execution functions like system() were restricted, the application failed to block other dangerous native PHP functions. An attacker with administrative privileges can inject malicious Smarty tags into modules such as Email Templates or Documents. By invoking functions like error_log() to write files or readgzfile() to read them, an attacker can achieve arbitrary file read/write, leading to full Remote Code Execution (RCE) and information disclosure. The issue is addressed in version 6.7.0 by extending the Smarty Security denylist.
Affected products
- CubeCart CubeCart < 6.7.0
Timeline
- 2026-04-29: advisory: GitHub Security Advisory published
- 2026-05-13: disclosed: CVE published to NVD