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

xibosignage

xibo-cms

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-52730 31 Aug 2026 < 4.4.3 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2026-42558 10 Jun 2026 < 4.4.2 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2026-42141 12 May 2026 < 4.4.1 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2026-31956 24 Apr 2026 < 4.4.1 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2026-31955 24 Apr 2026 < 4.4.1 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2026-31953 24 Apr 2026 < 4.4.1 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2026-31952 24 Apr 2026 >= 1.7, < 4.4.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-62369 4 Nov 2025 < 4.3.1 4.3.1. Update reference ↗
CVE-2024-43413 3 Sep 2024 < 4.1.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-43412 3 Sep 2024 < 4.1.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-41944 30 Jul 2024 => 2.1.0, < 3.3.12; => 4.0.0-alpha, < 4.0.14 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2024-41804 30 Jul 2024 => 2.1.0, < 3.3.12; => 4.0.0-alpha, < 4.0.14 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-41802 30 Jul 2024 => 1.8.0, < 3.3.12; => 4.0.0-alpha, < 4.0.14 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-41803 30 Jul 2024 => 2.1.0, < 3.3.12; => 4.0.0-alpha, < 4.0.14 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-29022 12 Apr 2024 >=1.8.0, < 3.3.10; >= 4.0.0, < 4.0.9 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2024-29023 12 Apr 2024 >= 1.8.0, < 3.3.10; >= 4.0.0, < 4.0.9 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2023-33181 30 May 2023 >= 3.0.0, < 3.3.5 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2023-33180 30 May 2023 >= 3.2.0, < 3.3.5 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2023-33179 30 May 2023 >= 3.2.0, < 3.3.5 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2023-33178 30 May 2023 >= 1.4.0, < 2.3.17; >= 3.0.0, < 3.3.5 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2023-33177 30 May 2023 >= 1.8.0, < 2.3.17; >= 3.0.0, < 3.3.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 ↗

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.