Quick answers
- Is CVE-2026-81568 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-81568 being exploited in the wild.
- How severe is CVE-2026-81568?
- Informational severity, with a CVSS score of 6.5, published 15 September 2026.
- Which products and versions are affected?
- J2Commerce J2Store 1.0.0-3.3.2, 4.0.0-4.0.22, 4.1.0-4.1.7.
- Is there a fix for CVE-2026-81568?
- 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-81568 attacked?
- It is attacked over the network, in a software library.
- Am I affected by CVE-2026-81568?
- Check whether anything you run is named in the advisory. 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 J2StoreModelOrderdownloads::getFilePath(), which constructs file paths by concatenating a configured attachment folder with a product file's stored name using only JPath::clean() and JFile::exists() checks. JPath::clean() normalizes path separators but does not resolve or reject directory traversal sequences (../ segments). An attacker with a valid download token and product ID can supply a crafted product_file_save_name containing ../ traversal sequences to escape the attachment folder and read any file accessible to the web server process, such as configuration.php containing database credentials. The traversal could be introduced through CSRF-forgeable admin product-file actions or other integration points. No evidence of wild exploitation has been reported.
Affected products
- J2Commerce J2Store 1.0.0-3.3.2, 4.0.0-4.0.22, 4.1.0-4.1.7
Timeline
- 2026-09-15: disclosed