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

devitemsllc

HT Mega Addons for Elementor – Elementor Widgets & Template Builder

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-11895 30 Sep 2026 HT Mega Addons for Elementor – Elementor Widgets & Template Builder: ≤ 3.1.1 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2025-13141 21 Nov 2025 ≤ 3.0.0 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2025-8068 31 Jul 2025 ≤ 2.9.1 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-2025-8401 31 Jul 2025 ≤ 2.9.1 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-2025-8151 31 Jul 2025 ≤ 2.9.1 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-2025-1802 20 Mar 2025 ≤ 2.8.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-2025-1261 8 Mar 2025 ≤ 2.8.2 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-12599 11 Feb 2025 ≤ 2.8.1 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-12597 4 Feb 2025 ≤ 2.7.6 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-8910 25 Sep 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-5215 26 Jun 2024 ≤ 2.5.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-5173 26 Jun 2024 ≤ 2.5.5 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2024-4876 21 May 2024 ≤ 2.5.2 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-4875 21 May 2024 ≤ 2.5.2 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-3990 9 May 2024 ≤ 2.5.0 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-3989 9 May 2024 ≤ 2.5.0 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2024-3307 2 May 2024 ≤ 2.4.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-2084 2 May 2024 ≤ 2.4.6 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2023-6214 2 May 2024 ≤ 2.4.6 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-2790 2 May 2024 ≤ 2.4.8 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-3308 2 May 2024 ≤ 2.4.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-2085 2 May 2024 ≤ 2.4.6 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-1974 9 Apr 2024 ≤ 2.4.6 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-1421 12 Mar 2024 ≤ 2.4.4 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2024-1397 12 Mar 2024 ≤ 2.4.6 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 ↗

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.