CordysCRM

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-2026-76899	18 Sep 2026	CordysCRM: < 1.7.4	1.7.4.	Update reference ↗
CVE-2026-76902	18 Sep 2026	CordysCRM: < 1.7.4	1.7.4.	Update reference ↗
CVE-2026-76900	18 Sep 2026	CordysCRM: = 1.7.3	1.7.4.	Update reference ↗
CVE-2026-76901	18 Sep 2026	CordysCRM: < 1.7.4	1.7.4.	Update reference ↗
CVE-2026-63647	18 Sep 2026	CordysCRM: < 1.7.2	No fixed version is explicitly recorded in the structured CVE data.	Use CVE record
CVE-2026-63646	18 Sep 2026	CordysCRM: < 1.7.2	1.7.2.	Update reference ↗
CVE-2026-52745	18 Sep 2026	CordysCRM: < 1.7.0	1.7.0.	Update reference ↗
CVE-2026-16223	19 Jul 2026	1.4.0; 1.4.1	No fixed version is explicitly recorded in the structured CVE data.	Use CVE record
CVE-2026-16222	19 Jul 2026	1.4.0; 1.4.1	No fixed version is explicitly recorded in the structured CVE data.	Use CVE record
CVE-2026-10567	2 Jun 2026	1.4.0; 1.4.1	1.7.0	Update reference ↗
CVE-2026-10514	1 Jun 2026	1.6.0; 1.6.1; 1.6.2	1.7.0	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.