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

latepoint

LatePoint – Calendar Booking Plugin for Appointments and Events

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-5356 8 Jul 2026 ≤ 5.4.0 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2026-11398 3 Jul 2026 ≤ 5.6.1 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2026-12657 2 Jul 2026 ≤ 5.6.2 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2026-13228 1 Jul 2026 ≤ 5.6.3 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2026-8176 16 Jun 2026 ≤ 5.5.1 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2026-9719 5 Jun 2026 ≤ 5.6.0 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2026-5365 14 May 2026 ≤ 5.3.2 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2026-7652 9 May 2026 ≤ 5.5.0 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2026-7332 6 May 2026 ≤ 5.5.0 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2026-7457 6 May 2026 ≤ 5.5.0 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2026-6741 27 Apr 2026 ≤ 5.4.1 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2026-5234 17 Apr 2026 ≤ 5.3.2 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2026-4785 8 Apr 2026 ≤ 5.3.0 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2026-2324 11 Mar 2026 ≤ 5.2.7 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2026-1487 3 Mar 2026 ≤ 5.2.7 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2026-1566 2 Mar 2026 ≤ 5.2.7 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2025-14873 14 Feb 2026 ≤ 5.2.5 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2026-1537 12 Feb 2026 ≤ 5.2.6 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2026-0617 3 Feb 2026 ≤ 5.2.5 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2025-7052 30 Sep 2025 ≤ 5.1.94 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2025-7038 30 Sep 2025 ≤ 5.1.94 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2025-6941 30 Sep 2025 ≤ 5.1.94 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2025-6815 30 Sep 2025 ≤ 5.1.94 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2025-3769 14 May 2025 ≤ 5.1.92 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.