JetFormBuilder · Security record
Is JetFormBuilder safe?
No known vulnerability affects the current version (3.6.8.1). 28 issues were found in earlier versions and fixed, the latest disclosed on Nov 1, 2026.
Checked 4 days ago against the WPVulnerability database, for version 3.6.8.1.
How it’s looked after
- Last release
- Nov 6, 2026 (2 days ago)
- Releases in the last year
- 28
- Tested up to
- WordPress 7.0.8
- Support resolved
- 0 of 2 threads in two months
- Active installs
- 80K+
28 known vulnerabilities
- 2 critical
- 10 high
- 14 medium
- 2 not rated
None affects the current version.
Disclosed each year
- 20233
- 20241
- 20253
- 202621
Every known vulnerability in JetFormBuilder
Newest first, with any that affect the current version at the top.
Fixed in 3.6.8 · CVE-2026-119480 · Nov 1, 2026 · CVE
Fixed in 3.6.8 · CVE-2026-119482 · Oct 30, 2026 · CVE
Fixed in 3.6.8 · CVE-2026-119479 · Oct 30, 2026 · CVE
Fixed in 3.6.6.1 · CVE-2026-107431 · Oct 9, 2026 · Wordfence
Fixed in 3.6.6.1 · CVE-2026-103912 · Oct 1, 2026 · Wordfence
Fixed in 3.6.6 · CVE-2026-102391 · Sep 30, 2026 · Wordfence
- high
Unauthenticated Stored Cross-Site Scripting via 'choice' Post Meta via Insert/Update Post Action
Fixed in 3.6.6 · CVE-2026-97342 · Sep 24, 2026 · Wordfence
- medium
Reflected Cross-Site Scripting via 'jfb_xss' (URL Query Variable) Parameter via Calculated Field
Fixed in 3.6.5.4 · CVE-2026-92212 · Sep 17, 2026 · Wordfence
Fixed in 3.6.5.3 · CVE-2026-19860 · Sep 15, 2026 · Wordfence
Fixed in 3.6.2.1 · CVE-2026-12793 · Sep 7, 2026 · Wordfence
Fixed in 3.6.5.2 · CVE-2026-84817 · Sep 7, 2026 · Wordfence
Fixed in 3.6.5.2 · CVE-2026-19859 · Sep 6, 2026 · Wordfence
Fixed in 3.6.5.2 · CVE-2026-19862 · Sep 6, 2026 · Wordfence
Fixed in 3.6.5.2 · CVE-2026-19861 · Sep 5, 2026 · Wordfence
Fixed in 3.6.5.2 · CVE-2026-19858 · Sep 3, 2026 · Wordfence
Fixed in 3.6.4.2 · CVE-2026-28140 · Jul 1, 2026 · Wordfence
- medium
Missing Authorization to Unauthenticated Sensitive Information Disclosure via 'context' Parameter
Fixed in 3.6.3.1 · CVE-2026-13459 · Jul 1, 2026 · Wordfence
Fixed in 3.6.1 · CVE-2026-54195 · Jun 16, 2026 · Wordfence
Fixed in 3.6.1.1 · CVE-2026-54196 · Jun 16, 2026 · Wordfence
Fixed in 3.5.6.2 · CVE-2026-32525 · Mar 23, 2026 · Wordfence
Fixed in 3.5.6.3 · CVE-2026-4373 · Mar 20, 2026 · Wordfence
Fixed in 3.5.4 · CVE-2025-11991 · Dec 15, 2025 · Wordfence
- medium
Missing Authorization
Fixed in 3.5.4 · CVE-2025-64384 · Nov 13, 2025 · Wordfence
Fixed in 3.5.2 · CVE-2025-53990 · Jul 16, 2025 · Wordfence
Fixed in 3.3.4.2 · CVE-2024-7291 · Aug 2, 2024 · Wordfence
Fixed in 3.1.5 · CVE-2023-48763 · Nov 28, 2023 · Wordfence
Fixed in 3.0.9 · CVE-2023-37866 · Jul 10, 2023 · Wordfence
Fixed in 3.0.7 · CVE-2023-33212 · May 22, 2023 · Wordfence
Questions about JetFormBuilder’s security
Is JetFormBuilder safe to use?
No known vulnerability affects its current version. Earlier versions had issues that are now fixed, so keep JetFormBuilder updated: most attacks target sites that haven’t updated.
Does JetFormBuilder have known security vulnerabilities?
None that affect the current version. WPVulnerability’s database lists 28 older issues, fixed in earlier versions, so keep JetFormBuilder up to date.
Is JetFormBuilder still maintained?
Yes. Its last release was 2 days ago. Its authors resolved 0 of the 2 support threads opened in the last two months.
Is JetFormBuilder compatible with the latest WordPress?
It’s tested up to WordPress 7.0.8, one version behind the current 7.1. Authors often update this line a few weeks after a release.
Hear about the next one first
Track your plugin on TrackWP and get an alert when a new vulnerability affecting it is published. Every plan has it, the free Starter too; Boost and FullCharge email it at once.
Start freeVulnerability data from WPVulnerability (CC0), which gathers records from CVE, Wordfence, Patchstack and WPScan. A clean record isn’t a guarantee: keep every plugin updated.