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

stellarwp

Kadence Blocks — Page Builder Toolkit for Gutenberg Editor

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-18062 1 Aug 2026 ≤ 3.7.8.1 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2026-18435 1 Aug 2026 ≤ 3.7.8 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2026-15286 10 Jul 2026 ≤ 3.5.32 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2026-12902 1 Jul 2026 ≤ 3.7.7 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2026-12904 1 Jul 2026 ≤ 3.7.7 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2026-11357 18 Jun 2026 ≤ 3.7.5 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2026-2826 4 Apr 2026 ≤ 3.6.3 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2026-2633 18 Feb 2026 ≤ 3.6.1 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2026-1857 18 Feb 2026 ≤ 3.6.1 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2026-2608 17 Feb 2026 ≤ 3.5.32 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2025-5678 9 Jul 2025 ≤ 3.5.10 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2025-1291 1 Mar 2025 ≤ 3.4.9 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2024-12304 11 Jan 2025 ≤ 3.4.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-12581 13 Dec 2024 ≤ 3.2.53 No fixed version is explicitly recorded in the structured CVE data. Update reference ↗
CVE-2024-10785 21 Nov 2024 ≤ 3.3.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-9655 1 Nov 2024 ≤ 3.3.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-5819 29 Jun 2024 ≤ 3.2.45 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-5289 27 Jun 2024 ≤ 3.2.42 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2024-4863 14 Jun 2024 ≤ 3.2.38 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-4208 15 May 2024 ≤ 3.2.37 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-3189 15 May 2024 ≤ 3.2.37 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-4209 11 May 2024 ≤ 3.2.36 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-4481 10 May 2024 ≤ 3.2.36 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-2273 2 May 2024 ≤ 3.2.34 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2024-1999 9 Apr 2024 ≤ 3.2.25 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-2023-6964 9 Apr 2024 ≤ 3.1.26 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2024-0598 9 Apr 2024 ≤ 3.2.17 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-2919 4 Apr 2024 ≤ 3.2.31 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-1541 13 Mar 2024 ≤ 3.2.23 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.