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

thehappymonster

Happy Addons for Elementor

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-2917 11 Mar 2026 ≤ 3.21.0 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2026-2918 11 Mar 2026 ≤ 3.21.0 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2026-1210 3 Feb 2026 ≤ 3.20.7 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2025-14635 23 Dec 2025 ≤ 3.20.3 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2024-12852 8 Jan 2025 ≤ 3.15.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-10538 12 Nov 2024 ≤ 3.12.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-8801 24 Sep 2024 ≤ 3.12.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-6627 27 Jul 2024 ≤ 3.11.2 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2024-5790 29 Jun 2024 ≤ 3.11.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-5041 31 May 2024 ≤ 3.10.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-5347 31 May 2024 ≤ 3.10.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-5088 18 May 2024 ≤ 3.10.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-4865 18 May 2024 ≤ 3.10.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-4391 16 May 2024 ≤ 3.10.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-4478 16 May 2024 ≤ 3.10.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-3891 2 May 2024 ≤ 3.10.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-3724 2 May 2024 ≤ 3.10.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-3890 26 Apr 2024 ≤ 3.10.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-1498 9 Apr 2024 ≤ 3.10.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-2787 9 Apr 2024 ≤ 3.10.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-2789 9 Apr 2024 ≤ 3.10.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-1387 9 Apr 2024 ≤ 3.10.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-2788 9 Apr 2024 ≤ 3.10.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-2786 9 Apr 2024 ≤ 3.10.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-1377 7 Mar 2024 ≤ 3.10.3 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2024-1366 7 Mar 2024 ≤ 3.10.3 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2024-0838 20 Feb 2024 ≤ 3.10.1 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2024-0438 20 Feb 2024 ≤ 3.10.1 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.