Quick answers
- Is CVE-2026-74252 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-74252 being exploited in the wild.
- How severe is CVE-2026-74252?
- Informational severity, with a CVSS score of 7.1, published 21 August 2026.
- Which products and versions are affected?
- J2commerce.Com J2Commerce 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-74252?
- 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-74252 attacked?
- It is attacked over the network, in a software library.
- Am I affected by CVE-2026-74252?
- Check whether you run J2commerce.Com J2Commerce 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 a stored cross-site scripting (XSS) flaw in J2Commerce guest checkout that exploits a filter bypass in Joomla's Input::getArray() method combined with PHP's default variables_order configuration (EGPCS), where cookies override POST parameters in $_REQUEST. Unauthenticated attackers can inject unsanitized HTML and JavaScript into billing address fields (such as billing_first_name) during guest checkout. The malicious payload is stored in the application database without proper sanitization. When administrators or other users view the affected orders or customer data, the stored XSS payload executes in their browsers, potentially allowing session hijacking, credential theft, or administrative account compromise. The vulnerability affects J2Store versions 1.0.0 through 3.3.20, 4.0.0 through 4.0.20, and 4.1.0 through 4.1.5, with no patch information currently available.
Affected products
- j2commerce.com J2Commerce 1.0.0-3.3.20, 4.0.0-4.0.20, 4.1.0-4.1.5
Timeline
- 2026-08-21: disclosed