JetFormBuilder <= 3.6.3 - Missing Authorization to Unauthenticated Sensitive Information Disclosure via 'context' Parameter
The JetFormBuilder — Dynamic Blocks Form Builder plugin for WordPress is vulnerable to authorization bypass in all versions up to, and including, 3.6.3. This is due to the plugin not properly verifying that a user is authorized to perform an action. This makes it possible for unauthenticated attackers to retrieve every distinct value stored under any arbitrary wp_postmeta key on the site — including WooCommerce billing PII such as _billing_email, _billing_phone, and _billing_address fields, order totals, attachment paths, and any third-party plugin credentials or tokens stored in post meta — provided at least one published JetFormBuilder form with a get_from_db generator field exists on the site. Exploitation requires that the target site has at least one published jet-form-builder post containing a field whose generator_function is set to get_from_db; an attacker must supply a matching form ID, field name, and generator ID in the request, but all of these can be discovered by browsing the site's public forms.
Quick answer
JetFormBuilder — Dynamic Blocks Form Builder should be reviewed and updated if it matches the affected versions. The recommended fix is to apply the vendor-supported patched version or the mitigation steps below, then retest the public website with Fixnx.
Who is affected
Affected versions
- *-3.6.3
Fixed versions
- 3.6.3.1
How to fix it
JetFormBuilder - Dynamic Blocks Form Builder is affected by CVE-2026-13459, missing authorization that can expose sensitive information through the context parameter in *-3.6.3. Prioritize production WordPress sites where the plugin or theme is enabled, especially if unauthenticated users can reach the vulnerable workflow. The recommended remediation is to update to version 3.6.3.1 or a newer vendor-supported patched release. If immediate patching is not possible, reduce exposure, restrict access to the vulnerable feature, and monitor logs until the vendor-supported fix is in place.
- Inventory every WordPress site that uses JetFormBuilder - Dynamic Blocks Form Builder, including production, staging, multisite, customer, and managed environments.
- Confirm the installed plugin or theme version and compare it with the affected range: *-3.6.3.
- Apply the remediation: update to version 3.6.3.1 or a newer vendor-supported patched release.
- If the update cannot be applied immediately, disable JetFormBuilder - Dynamic Blocks Form Builder or restrict the affected admin, REST, AJAX, shortcode, upload, booking, ecommerce, profile, form, gallery, or theme workflow to trusted administrators only.
- Review application, web server, WordPress security plugin, WAF, authentication, and administrator activity logs for attempts related to CVE-2026-13459.
- Remove suspicious stored content, uploaded files, generated logs, injected scripts, unexpected appointments/orders/posts, or altered configuration created through the affected workflow.
- Clear application, object, page, CDN, and browser caches after remediation so stale vulnerable responses or stored payloads are not served.
Scan now. Google sign-in is only needed to unlock fix guidance.
Verify the fix
- Confirm JetFormBuilder - Dynamic Blocks Form Builder is no longer running *-3.6.3 and record the patched or mitigated version in the remediation ticket.
- Verify unauthenticated users can no longer trigger the affected action or access data outside their intended permissions.
- Review logs before and after the fix for exploitation attempts, suspicious role activity, unexpected content changes, file reads, SQL errors, or unauthorized data access.
- Rerun a Fixnx scan and any relevant plugin, WAF, or manual regression checks to confirm public exposure is reduced.
- Document the advisory, affected assets, remediation action, verification evidence, and any cleanup or credential rotation performed.
Related categories
Trusted references
FAQ
What is affected by CVE-2026-13459?
JetFormBuilder — Dynamic Blocks Form Builder versions listed as affected should be reviewed: *-3.6.3.
What should I fix first?
Start with internet-facing sites, admin panels, login flows, plugins, themes, modules, packages, and systems that process user-controlled input or sensitive data.
How do I confirm the fix worked?
Apply the patched version or mitigation, clear caches where relevant, retest the affected workflow, and run a new Fixnx scan to verify public website exposure signals.
How are Fixnx security risk categories chosen?
Fixnx keeps one canonical risk page and assigns only broad, relevant categories such as ecosystem, technology area, or vulnerability class.