Quick answers
- Is CVE-2026-78069 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-78069 being exploited in the wild.
- How severe is CVE-2026-78069?
- Informational severity, 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-78069?
- 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-78069 attacked?
- It is attacked over the network, in a software library.
- Am I affected by CVE-2026-78069?
- 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 exists in the `J2StoreControllerApps::appTask` delegation path, which instantiates app-plugin controllers without ACL authorization checks. The missing authorization is masked only by a side effect of `fof.xml`'s wildcard-deny rule that resolves under the singularized ACL key `app` (which has no explicit allow rule). Behind this delegation path, the `applocalizationdata::getInstallerTool()` method uses a caller-influenced table name parameter without an allowlist to both select `#__j2store_*` tables for truncation and construct a file path to load and execute SQL files. This combination enables path-traversal-capable file read and arbitrary SQL execution. The vulnerability affects J2Store versions 1.0.0–3.3.21, 4.0.0–4.0.21, and 4.1.0–4.1.6.
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