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

highwarden

Super Store Finder

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-81768 31 Aug 2026 n/a ≤ 7.10 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2025-58939 29 Oct 2025 Super Store Finder: ≤ 7.5 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2025-47571 9 Sep 2025 ≤ 7.8 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2025-49413 20 Aug 2025 ≤ 7.6 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2025-52720 14 Aug 2025 ≤ 7.5 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2025-39445 19 May 2025 ≤ 7.2 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2024-43975 17 Sep 2024 ≤ 6.9.7 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2024-43976 17 Sep 2024 ≤ 6.9.7 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2024-43978 17 Sep 2024 ≤ 6.9.8 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.