JetFormBuilder <= 3.6.2 - Missing Authorization to Unauthenticated JetEngine Options Page Modification
Strategic Overview
- Status
- Patched in 3.6.2.1
- Affected Plugin
- JetFormBuilder — Dynamic Blocks Form Builder
- Affected Version
<= 3.6.2- CVSS
- 5.3Medium
- Weakness type
- CWE-862 · Missing Authorization
- CVE
CVE pending
At a glance
This record tracks a medium-severity Missing Authorization vulnerability in the JetFormBuilder WordPress plugin, affecting versions <= 3.6.2. It carries a CVSS score of 5.3 (reachable over the network; low attack complexity). Exploitation requires no authentication. The issue is fixed in version 3.6.2.1; sites on affected versions should update now. Disclosed September 2026, reported by andrea bocchetti.
Vulnerability Overview
The JetFormBuilder — Dynamic Blocks Form Builder plugin for WordPress is vulnerable to unauthorized modification of data due to a missing capability check on the 'do_action' function in the 'Update_Options' action class in all versions up to, and including, 3.6.2. This makes it possible for unauthenticated attackers to modify JetEngine Options Page values when an administrator has configured a form with the "Update Options" post-submission action. The vulnerability requires that both JetFormBuilder and JetEngine are installed and active, and that an administrator has specifically configured a form with the Update Options action.
Technical Analysis
The vector marks this flaw as remotely reachable over the network, with low attack complexity — no special timing or configuration is needed, and no privileges on the target site, and no interaction from a victim user.
CWE-862: Missing Authorization
JetFormBuilder <= 3.6.2 carries this weakness at do_action, and reaching it takes no account at all. A missing authorization check means a function is reachable by anyone who can reach the endpoint, because the code never asks whether the caller is allowed to perform the action.
Any user who can reach the endpoint gets to run an action reserved for higher-privileged roles, from reading protected data to changing settings or content. For JetFormBuilder the fix is 3.6.2.1: builds <= 3.6.2 are affected, anything from 3.6.2.1 onward is not.
Remediation
Update to version 3.6.2.1, or a newer patched version
How does WordSec protect against this?
This one needs no account at all, which puts it outside what login hardening can reach; WordSec's login security narrows the account-level paths around it, and the firewall is what inspects the request itself. None of that substitutes for the fix: JetFormBuilder 3.6.2.1 closes this, and updating the plugin is the step that ends it.
- Login Security
- Alerts
External References
Related records
Same weakness class
- 5.3CVE-2026-28140: JetFormBuilder Missing Authorization
CVE-2026-28140 - 5.3CVE-2026-13459: JetFormBuilder Unauthenticated Info Disclosure
CVE-2026-13459 - 5.3CVE-2025-11991: JetFormBuilder Unauthenticated Form Generation
CVE-2025-11991 - 5.3CVE-2025-64384: JetFormBuilder <= 3.5.3 Missing Authorization
CVE-2025-64384
Other vulnerabilities in JetFormBuilder — Dynamic Blocks Form Builder
- 8.8CVE-2026-54196: JetFormBuilder Privilege Escalation
CVE-2026-54196 - 8.8CVE-2026-32525: JetFormBuilder — Dynamic Blocks Form Builder RCE
CVE-2026-32525 - 8.8CVE-2023-37866: JetFormBuilder <= 3.0.8 Privilege Escalation
CVE-2023-37866 - 7.5CVE-2026-4373: JetFormBuilder <= 3.5.6.2 Arbitrary File Read
CVE-2026-4373 - 7.2CVE-2026-54195: JetFormBuilder Stored XSS
CVE-2026-54195 - 7.2CVE-2024-7291: JetFormBuilder <= 3.3.4.1 Privilege Escalation
CVE-2024-7291 - 6.6CVE-2025-53990: JetFormBuilder <= 3.5.1.2 PHP Object Injection
CVE-2025-53990 - 5.3CVE-2023-48763: JetFormBuilder <= 3.1.4 Content Injection
CVE-2023-48763
Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C