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

Jetmonsters

JetFormBuilder

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-102391 30 Sep 2026 JetFormBuilder: n/a ≤ 3.6.5.4 Update the WordPress JetFormBuilder - Dynamic Blocks Form Builder plugin to the latest available version (at least 3.6.6). Update reference ↗
CVE-2026-28140 6 Aug 2026 n/a ≤ 3.6.4.1 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2026-54196 17 Jun 2026 JetFormBuilder: n/a ≤ 3.6.1 Update the WordPress JetFormBuilder Plugin to the latest available version (at least 3.6.1.1). Update reference ↗
CVE-2026-54195 17 Jun 2026 n/a ≤ 3.6.0.1 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2026-32525 25 Mar 2026 n/a ≤ <= 3.5.6.1 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2025-64384 13 Nov 2025 JetFormBuilder: ≤ 3.5.3 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2025-53990 16 Jul 2025 ≤ 3.5.1.2 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.