CVE-2026-78000: Joomla Extension - j2commerce.com - Open redirect in cart controller in J2Store 1.0.0-3.3.20, 4.0.0-4.0.20, 4.1.0-4.1.5

Published Sep 3, 2026
·
Updated

Joomla Extension - j2commerce.com - Reflected XSS via filtertag, pricefrom and priceto in J2Store 1.0.0-3.3.21, 4.0.0-4.0.21, 4.1.0-4.1.6 - Four task handlers accepted a base64-encoded URL from user input and redirected to it without validating the destination host, enabling phishing using the shop's trusted domain. No authentication required.

Affected Software

2 affected components
J2Store J2Store>=1.0.0<=3.3.20, >=4.0.0<=4.0.20, >=4.1.0<=4.1.5
J2Store J2Store>=1.0.0<=3.3.21, >=4.0.0<=4.0.21, >=4.1.0<=4.1.6

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade j2commerce.com/J2Store to a version that resolves this vulnerability.

    Fixed in 1.0.0-3.3.20
  2. Upgrade

    Upgrade j2commerce.com/J2Store to a version that resolves this vulnerability.

    Fixed in 1.0.0-3.3.21
  3. Upgrade

    Upgrade j2commerce.com/J2Store to a version that resolves this vulnerability.

    Fixed in 4.0.0-4.0.20
  4. Upgrade

    Upgrade j2commerce.com/J2Store to a version that resolves this vulnerability.

    Fixed in 4.0.0-4.0.21
  5. Upgrade

    Upgrade j2commerce.com/J2Store to a version that resolves this vulnerability.

    Fixed in 4.1.0-4.1.5
  6. Upgrade

    Upgrade j2commerce.com/J2Store to a version that resolves this vulnerability.

    Fixed in 4.1.0-4.1.6

Event History

Sep 3, 2026
CVE Published
via MITRE·11:59 AM
Data Sourced
via MITRE·11:59 AM
DescriptionWeakness

Frequently Asked Questions

1

Does exploitation require an authenticated Joomla or J2Store account?

No. The record states that no authentication is required.

2

What must an attacker be able to provide to trigger the redirect behavior?

An attacker needs to supply a base64-encoded URL to one of the four affected task handlers. The handlers redirect to the supplied URL without validating its destination host, which can support phishing through the shop's trusted domain.

3

Is the affected-version scope consistent in this record?

No. The title lists redirect-related ranges ending in 3.3.20, 4.0.20, and 4.1.5, while the description refers to reflected XSS and ranges ending in 3.3.21, 4.0.21, and 4.1.6. The supplied data does not resolve this discrepancy.

4

Does the record provide a temporary mitigation for environments that cannot patch immediately?

No temporary mitigation or configuration workaround is provided in the supplied data.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203