Quick answers
- Is CVE-2026-78064 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-78064 being exploited in the wild.
- How severe is CVE-2026-78064?
- Informational severity, with a CVSS score of 7.5, published 3 September 2026.
- Which products and versions are affected?
- J2commerce.Com J2Store 1.0.0-3.3.21, 4.0.0-4.0.21, 4.1.0-4.1.6.
- Is there a fix for CVE-2026-78064?
- 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-78064 attacked?
- It is attacked over the network, in a web application.
- Am I affected by CVE-2026-78064?
- Check whether you run J2commerce.Com J2Store 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
The vulnerability is an authorization bypass in the J2Store cart controller (J2StoreControllerCarts). The `fof.xml` configuration grants a wildcard ACL permission to all cart view tasks, and the Framework-on-Framework (FOF) library only enforces CSRF tokens on back-end HTML requests, not on front-end `format=raw` requests. While the extension properly scoped the `remove()` task to the caller's own session, it failed to override the generic FOF `save` task, leaving it reachable from the front-end. An attacker can invoke this task with attacker-controlled `user_id` and `session_id` parameters to insert new cart rows or overwrite existing ones. No authentication is required; the vulnerability is reachable via network requests.
Affected products
- j2commerce.com J2Store 1.0.0-3.3.21, 4.0.0-4.0.21, 4.1.0-4.1.6
Timeline
- 2026-09-03: disclosed: Vulnerability published on NVD