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

LimeSurvey GmbH

LimeSurvey

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-102626 2 Oct 2026 LimeSurvey: 7.4.0 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2026-97685 29 Sep 2026 LimeSurvey: 7.3.0 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2026-92730 23 Sep 2026 LimeSurvey: 7.0.14 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2026-91775 23 Sep 2026 LimeSurvey: 7.0.14 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2026-65931 27 Aug 2026 7.0.5 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2026-63360 26 Aug 2026 7.0.5 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2026-16809 26 Aug 2026 7.0.5 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2026-65930 26 Aug 2026 7.0.5 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2026-15973 26 Aug 2026 7.0.5 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2026-18403 14 Aug 2026 7.0.5 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2026-63361 14 Aug 2026 7.0.5 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2026-63107 20 Jul 2026 ≤ 6.17.10; ≤ 7.0.4 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2026-50636 9 Jun 2026 LimeSurvey: ≤ 7.0 LimeSurvey: 7.0.1 Update reference ↗
CVE-2026-50635 9 Jun 2026 LimeSurvey: ≤ 7.0 LimeSurvey: 7.0.1 Update reference ↗
CVE-2020-36993 28 Jan 2026 ≤ 4.3.10 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-41076 20 Nov 2025 6.13.0 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2025-41075 20 Nov 2025 6.13.0 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2025-41074 20 Nov 2025 6.13.0 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2025-41376 1 Aug 2025 3.0 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2025-41375 1 Aug 2025 3.0 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2025-34120 16 Jul 2025 2.0+ ≤ 2.06+ Build 151014 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.