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

jegtheme

Jeg Kit for Elementor – Powerful Addons for Elementor, Widgets & Templates for WordPress

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-100180 3 Oct 2026 Jeg Kit for Elementor – Powerful Addons for Elementor, Widgets & Templates for WordPress: ≤ 3.2.19 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2026-18405 18 Sep 2026 Jeg Kit for Elementor – Powerful Addons for Elementor, Widgets & Templates for WordPress: ≤ 3.2.16 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2026-2916 1 Aug 2026 ≤ 3.1.1 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2026-13710 10 Jul 2026 ≤ 3.2.6 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2026-6916 2 May 2026 ≤ 3.1.0 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2025-14275 8 Jan 2026 ≤ 3.0.1 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2025-2944 10 May 2025 ≤ 2.6.12 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2024-13217 27 Feb 2025 ≤ 2.6.11 An authoritative update reference is available, but the fixed version is not recorded in the structured CVE fields. Check the linked vendor advisory for the applicable release. Update reference ↗
CVE-2024-10308 26 Nov 2024 ≤ 2.6.9 An authoritative update reference is available, but the fixed version is not recorded in the structured CVE fields. Check the linked vendor advisory for the applicable release. Update reference ↗
CVE-2024-8899 26 Nov 2024 ≤ 2.6.9 An authoritative update reference is available, but the fixed version is not recorded in the structured CVE fields. Check the linked vendor advisory for the applicable release. Update reference ↗
CVE-2024-6804 27 Aug 2024 ≤ 2.6.7 An authoritative update reference is available, but the fixed version is not recorded in the structured CVE fields. Check the linked vendor advisory for the applicable release. Update reference ↗
CVE-2024-4479 15 Jun 2024 ≤ 2.6.5 An authoritative update reference is available, but the fixed version is not recorded in the structured CVE fields. Check the linked vendor advisory for the applicable release. Update reference ↗
CVE-2024-3161 2 May 2024 ≤ 2.6.4 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2024-3819 2 May 2024 ≤ 2.6.4 An authoritative update reference is available, but the fixed version is not recorded in the structured CVE fields. Check the linked vendor advisory for the applicable release. Update reference ↗
CVE-2024-0334 1 May 2024 ≤ 2.6.4 An authoritative update reference is available, but the fixed version is not recorded in the structured CVE fields. Check the linked vendor advisory for the applicable release. Update reference ↗
CVE-2024-3162 3 Apr 2024 ≤ 2.6.3 An authoritative update reference is available, but the fixed version is not recorded in the structured CVE fields. Check the linked vendor advisory for the applicable release. Update reference ↗
CVE-2024-1327 3 Apr 2024 ≤ 2.6.3 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2024-1326 12 Mar 2024 ≤ 2.6.2 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2022-3794 22 Dec 2022 ≤ 2.5.6 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2022-3805 22 Dec 2022 ≤ 2.5.6 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.