Evidence-linked product lifecycle intelligenceSUPPORT · SECURITY · RETIREMENT
← Search results
CVE-LINKED INVENTORY17 SECURITY RECORDS

j2commerce.com

J2Store extension for Joomla

Affected and fixed version statements observed in the public BlackTree CVE catalogue. These statements describe vulnerability scope, not publisher support entitlement.

Lifecycle evidence status

This identity is present in BlackTree CVE records, but no product-specific publisher support or retirement history is currently registered in Lifecycle.

A missing support date does not mean the product is supported. CVE publication dates and affected-version ranges must not be interpreted as EOL dates.

CVE-observed version history

CVEPublishedAffected versionsFixed version informationPublisher evidence
CVE-2026-82190 15 Sep 2026 J2Store extension for Joomla: 1.0.0-3.3.22, 4.0.0-4.0.22, 4.1.0-4.1.7 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2026-78081 15 Sep 2026 J2Store extension for Joomla: 1.0.0-3.3.22, 4.0.0-4.0.22, 4.1.0-4.1.7 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2026-81568 15 Sep 2026 J2Store extension for Joomla: 1.0.0-3.3.22, 4.0.0-4.0.22, 4.1.0-4.1.7 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2026-82191 15 Sep 2026 J2Store extension for Joomla: 1.0.0-3.3.22, 4.0.0-4.0.22, 4.1.0-4.1.7 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2026-81567 15 Sep 2026 J2Store extension for Joomla: 1.0.0-3.3.22, 4.0.0-4.0.22, 4.1.0-4.1.7 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2026-82189 15 Sep 2026 J2Store extension for Joomla: 1.0.0-3.3.22, 4.0.0-4.0.22, 4.1.0-4.1.7 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2026-78000 3 Sep 2026 1.0.0-3.3.21; 4.0.0-4.0.21; 4.1.0-4.1.6 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2026-78069 3 Sep 2026 1.0.0-3.3.21; 4.0.0-4.0.21; 4.1.0-4.1.6 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2026-78065 3 Sep 2026 1.0.0-3.3.21; 4.0.0-4.0.21; 4.1.0-4.1.6 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2026-77999 3 Sep 2026 1.0.0-3.3.21; 4.0.0-4.0.21; 4.1.0-4.1.6 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2026-78064 3 Sep 2026 1.0.0-3.3.21; 4.0.0-4.0.21; 4.1.0-4.1.6 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2026-67361 21 Aug 2026 1.0.0-3.3.20; 4.0.0-4.0.20; 4.1.0-4.1.5 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2026-74252 21 Aug 2026 1.0.0-3.3.20; 4.0.0-4.0.20; 4.1.0-4.1.5 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2026-67358 21 Aug 2026 1.0.0-3.3.20; 4.0.0-4.0.20; 4.1.0-4.1.5 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2026-67362 21 Aug 2026 1.0.0-3.3.20; 4.0.0-4.0.20; 4.1.0-4.1.5 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2026-67359 21 Aug 2026 1.0.0-3.3.20; 4.0.0-4.0.20; 4.1.0-4.1.5 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2026-67360 21 Aug 2026 1.0.0-3.3.20; 4.0.0-4.0.20; 4.1.0-4.1.5 No fixed version is explicitly recorded in the structured CVE data. Use CVE record

How this record is maintained

The CVE inventory is reconciled automatically from cve.blacktree.nl. Exact identity matches link to existing Lifecycle product or package histories. Unmatched products stay in a prioritised publisher-source research queue, and Lifecycle marks the date gap instead of inferring a support boundary from vulnerability data.