Advisory

CVE-2026-119479 in JetFormBuilder

CVSS 5.3 (CVE record)Published Nov 5, 2026Last verified Nov 21, 2026

An unauthenticated attacker can inject arbitrary shortcodes into form field values in the JetFormBuilder plugin, leading to arbitrary code execution on the…

Exploited in the wild
Not reported
Installs not updated
At least 23.25%
Affected and fixed versions
ComponentAffectedFixed in
JetFormBuilder — Dynamic Blocks Form Builder (plugin)3.6.7.1 and earlier3.6.8
Run a free scan of your site

The free scan checks what is visible from outside your site. It does not log in, and it cannot confirm on its own whether this specific issue is present.

Summary

An Arbitrary Shortcode Execution vulnerability affects the JetFormBuilder — Dynamic Blocks Form Builder plugin for WordPress. This flaw allows unauthenticated attackers to inject malicious shortcodes through form submissions. A patch is available in version 3.6.8. There is no evidence of active exploitation.

Affected and patched versions

  • JetFormBuilder — Dynamic Blocks Form Builder (plugin jetformbuilder): affected 3.6.7.1 and earlier; fixed in 3.6.8

Is my site vulnerable?

To determine if your WordPress site is vulnerable, check the installed version of the JetFormBuilder — Dynamic Blocks Form Builder plugin.

  1. Log in to your WordPress administration dashboard.

  2. Navigate to the "Plugins" section and select "Installed Plugins".

  3. Locate "JetFormBuilder — Dynamic Blocks Form Builder" in the list.

  4. Examine the version number displayed next to the plugin name.

Your site is vulnerable if the installed version is 3.6.7.1 or earlier. If your site runs version 3.6.8 or newer, the vulnerability has been addressed. Regularly reviewing plugin versions helps maintain site security.

What an attacker actually does

The JetFormBuilder — Dynamic Blocks Form Builder plugin enables WordPress site administrators to create and manage various forms. These forms are designed to collect user input, which is then processed according to the form's configuration. The vulnerability arises from how the plugin handles user-supplied macro values within submitted form fields.

Specifically, the plugin fails to properly tokenize these user-supplied macro values before they are passed to the do_shortcode() function. In WordPress, shortcodes are special tags enclosed in square brackets, like [gallery] or [contact_form], that are interpreted by the system to execute specific functions or display dynamic content. When user input is not adequately sanitized or tokenized, the system can mistake malicious shortcode syntax for legitimate commands.

This oversight allows an unauthenticated attacker to inject arbitrary shortcodes directly into form field values. An "unauthenticated attacker" means that anyone, without needing an account or special permissions on the WordPress site, can submit a form containing these malicious shortcodes. When the form submission is processed by certain plugin actions—specifically "Send Email," "Call Webhook," "Redirect To Page," or "Media field settings"—the injected shortcodes are executed on the server. This execution effectively grants the attacker the ability to run arbitrary code on the server, a condition known as code injection. The impact of such an attack can range from defacing the website to gaining full control over the server, depending on the capabilities of the injected shortcode.

How to detect a compromise

Detecting a compromise related to this vulnerability involves examining various aspects of your WordPress installation and server environment for anomalies. The core issue is the injection and execution of shortcodes through form submissions, which can leave traces in the database, logs, and potentially the file system.

Begin by inspecting the WordPress database for unexpected shortcode patterns within stored form submission data. The JetFormBuilder plugin stores form entries, and malicious shortcodes would reside within these records. You can use WP-CLI to search across database tables for common shortcode syntax. For example, to search all tables for strings resembling shortcodes:

wp db search --all-tables --regex="\[[a-zA-Z0-9_-]+(\s[^\]]+)?\]"

Review the output for any unusual or unrecognized shortcodes, particularly in fields that store user-submitted text. Pay close attention to entries associated with forms configured to use "Send Email," "Call Webhook," "Redirect To Page," or "Media field settings," as these are the triggers for shortcode execution.

Beyond the database, examine server access logs and error logs. Look for unusual requests directed at form submission endpoints, or errors that might indicate failed or successful code execution attempts. If the "Call Webhook" action was exploited, your server's outbound network connections might show unexpected activity to external IP addresses or domains. Similarly, if "Send Email" was the trigger, check your mail server logs for unusual email volumes or content originating from your WordPress site.

Inspect the WordPress file system for newly created or modified files that are not part of legitimate plugin or theme updates. Attackers often use code injection to upload web shells or backdoors to maintain access. Focus on directories like wp-content/uploads/, wp-content/plugins/, or temporary directories. Use commands like find /path/to/wordpress -type f -newermt "YYYY-MM-DD HH:MM:SS" -ls to identify recently modified files, adjusting the timestamp to a period before and after any suspected compromise.

Finally, monitor your site's behavior. Unexpected redirects, defaced pages, or unusual resource consumption could indicate a successful attack. If you have a Web Application Firewall (WAF) in place, review its logs for blocked requests containing shortcode-like patterns in form submission parameters.

How to fix

Addressing the Arbitrary Shortcode Execution vulnerability in JetFormBuilder — Dynamic Blocks Form Builder requires specific actions to secure your site.

  1. Update the Plugin: The primary and most effective solution is to update the JetFormBuilder — Dynamic Blocks Form Builder plugin to version 3.6.8 or higher. This version includes a fix designed to prevent stored cross-site scripting (XSS) through preset values evaluated as macros, which directly addresses the underlying vulnerability. Always back up your site before performing any updates.

  2. Validate Input and Escape Output: If an immediate update is not feasible, implement robust input validation and output escaping. This involves ensuring that all user-supplied data is treated strictly as data, not as executable code.

    • When input is received, validate it against expected formats and types. Reject or sanitize any input that deviates from these expectations.

    • Before displaying user-supplied data on a web page or using it in an HTML attribute or JavaScript context, escape it appropriately. This converts special characters into their harmless entity equivalents, preventing them from being interpreted as code.

  3. Sanitize Stored Active Content: For any user-submitted data that is stored in your database, apply sanitization routines. This process cleans potentially malicious content, such as shortcodes or script tags, from the data before it is saved. This helps prevent the execution of malicious content when the stored data is later retrieved and processed.

  4. Consider Targeted Application Patch or Functionality Restriction: If updating is not possible and the risk is high, consider developing a targeted application patch. This would involve custom code to specifically address the missing tokenization logic in the vulnerable versions of the plugin. Alternatively, temporarily restrict or disable the affected functionality. This might mean disabling forms that use "Send Email," "Call Webhook," "Redirect To Page," or "Media field settings" until the plugin can be updated.

  5. Implement Mitigation with WAF Rules, Network Egress Filters, or Feature Flags:

    • WAF Rules: Configure your Web Application Firewall (WAF) to detect and block requests containing shortcode patterns in form submission parameters. This can act as a protective layer by filtering malicious input before it reaches the vulnerable plugin.

    • Network Egress Filters: Implement network egress filtering on your server. This restricts outbound connections from your web server to only approved destinations, which can help prevent an attacker from using a compromised site to communicate with external command-and-control servers or exfiltrate data, especially if the "Call Webhook" action is exploited.

    • Feature Flags: If the plugin or your application supports feature flags, use them to temporarily disable the specific form actions ("Send Email," "Call Webhook," "Redirect To Page," "Media field settings") that trigger the shortcode execution, thereby limiting the attack surface until a full patch can be applied.

Timeline

Date

Event

2026-10-30

NVD Publication

Sources

PowerSEC coverage
PowerSEC detects the affected versions on every plan, and has since November 6, 2026. No PowerSEC firewall rule blocks this attack. Update to 3.6.8 or later to remove the vulnerability.
This record contains material that is subject to copyright Copyright 2012-2026 Defiant Inc. Copyright 1999-2026 The MITRE Corporation
Hacked? Talk to us