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

appleple inc.

a-blog cms (Ver.3.1.x series)

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-2025-31103 31 Mar 2025 prior to Ver.3.1.37; prior to Ver.3.0.41; prior to Ver.2.11.70; prior to Ver.2.10.58; prior to Ver.2.9.46; prior to Ver.2.8.80 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2024-31396 22 May 2024 prior to Ver.3.1.12; prior to Ver.3.0.32 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2024-31395 22 May 2024 prior to Ver.3.1.12; prior to Ver.3.0.32; prior to Ver.2.11.61; prior to Ver.2.10.53; Ver.2.9 and earlier No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2024-31394 22 May 2024 prior to Ver.3.1.12; prior to Ver.3.0.32; prior to Ver.2.11.61; prior to Ver.2.10.53; Ver.2.9 and earlier No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2024-30420 22 May 2024 prior to Ver.3.1.12; prior to Ver.3.0.32 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2024-30419 22 May 2024 prior to Ver.3.1.12; prior to Ver.3.0.32; prior to Ver.2.11.61; prior to Ver.2.10.53; Ver.2.9 and earlier No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2024-27279 12 Mar 2024 Ver.3.1.9 and earlier; Ver.3.0.30 and earlier; Ver.2.11.59 and earlier; Ver.2.10.51 and earlier; Ver.2.9 and earlier No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2024-23782 28 Jan 2024 prior to Ver.3.1.7; prior to Ver.3.0.29; prior to Ver.2.11.58; prior to Ver.2.10.50; Ver.2.9.0 and earlier No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2024-23348 23 Jan 2024 prior to Ver.3.1.7; prior to Ver.3.0.29; prior to Ver.2.11.58; prior to Ver.2.10.50; Ver.2.9.0 and earlier No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2024-23183 23 Jan 2024 prior to Ver.3.1.7; prior to Ver.3.0.29; prior to Ver.2.11.58; prior to Ver.2.10.50; Ver.2.9.0 and earlier No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2024-23182 23 Jan 2024 prior to Ver.3.1.7; prior to Ver.3.0.29; prior to Ver.2.11.58; prior to Ver.2.10.50; Ver.2.9.0 and earlier No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2024-23181 23 Jan 2024 prior to Ver.3.1.7; prior to Ver.3.0.29; prior to Ver.2.11.58; prior to Ver.2.10.50; Ver.2.9.0 and earlier No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2024-23180 23 Jan 2024 prior to Ver.3.1.7; prior to Ver.3.0.29; prior to Ver.2.11.58; prior to Ver.2.10.50; Ver.2.9.0 and earlier 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.