Quick answers
- Is CVE-2026-78065 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-78065 being exploited in the wild.
- How severe is CVE-2026-78065?
- Informational severity, with a CVSS score of 4.3, published 3 September 2026.
- Which products and versions are affected?
- J2commerce.Com J2Store 1.0.0-3.3.21, 4.0.0-4.1.6.
- Is there a fix for CVE-2026-78065?
- 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-78065 attacked?
- It is attacked over the network, in a software library.
- Am I affected by CVE-2026-78065?
- 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 Insecure Direct Object Reference (IDOR) flaw in the `editAddress()` function. The vulnerable code checks whether a logged-in user owns an address by validating that the `user_id` field is non-empty and belongs to a different user; however, guest-checkout address records have a null or empty `user_id`, so this ownership check is never triggered. Any authenticated user can access the address edit form by guessing or incrementing the `address_id` parameter, causing the guest customer's personal information to be prefilled into the form. No special privileges or user interaction required beyond Joomla account login. Affected versions are J2Store 1.0.0–3.3.21 and 4.0.0–4.1.6; a patch should implement proper access control on all address records regardless of `user_id` state.
Affected products
- j2commerce.com J2Store 1.0.0-3.3.21, 4.0.0-4.1.6
Timeline
- 2026-09-03: disclosed