Appspider Pro

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

CVE	Published	Affected versions	Fixed version information	Publisher evidence
CVE-2025-11195	30 Sep 2025	< 7.5.021	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-36857	25 Sep 2025	< 7.5.021	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-4951	20 May 2025	Below 7.5.018	No fixed version is explicitly recorded in the structured CVE data.	Use CVE record
CVE-2017-5240	3 May 2017	All version prior to 6.14.060	No fixed version is explicitly recorded in the structured CVE data.	Use CVE record
CVE-2017-5236	3 May 2017	All version prior to 6.14.060	No fixed version is explicitly recorded in the structured CVE data.	Use CVE record
CVE-2017-5233	2 Mar 2017	All versions prior to version 6.14.053	No fixed version is explicitly recorded in the structured CVE data.	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.