Quick answers
- Is CVE-2026-67358 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-67358 being exploited in the wild.
- How severe is CVE-2026-67358?
- Informational severity, with a CVSS score of 0, published 21 August 2026.
- Which products and versions are affected?
- J2commerce.Com J2Store 1.0.0-3.3.20, 4.0.0-4.0.20, 4.1.0-4.1.5.
- Is there a fix for CVE-2026-67358?
- 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-67358 attacked?
- It is attacked over the network, in a web application.
- Am I affected by CVE-2026-67358?
- 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 access control bypass combined with CSRF weakness in J2Store's download limit endpoint. An authenticated user with a valid order token can manipulate the download counter for digital products belonging to other orders by sending requests to the download quota management endpoint. The endpoint does not properly validate that the requesting user owns the order being modified, nor does it implement CSRF tokens to prevent forged requests. An attacker can incrementally increase download limits or reset counters, effectively bypassing licensing controls on digital products. Affected versions span J2Store 1.0.0–3.3.20, 4.0.0–4.0.20, and 4.1.0–4.1.5; patches are expected from the vendor.
Affected products
- j2commerce.com J2Store 1.0.0-3.3.20, 4.0.0-4.0.20, 4.1.0-4.1.5
Timeline
- 2026-08-21: disclosed