⚠ Reference material — not professional advice. Test in staging, back up first, verify against your specific version. Use your own judgment for your environment.
● High · CVSS 7.5

How to Fix CVE-2026-4373: Path Traversal in JetFormBuilder, Dynamic Blocks Form Builder

Other vulnerabilities in the same area that are worth patching alongside this one:

*By Sai Kiran Pandrala*

⚡ At a glance
SeverityCVSS 7.5 - High
Actively exploited?Not currently listed in CISA KEV
Affected0 <= 3.5.6.2
Fixed inSee vendor advisory
Type (CWE)CWE-36: Absolute Path Traversal

What is CVE-2026-4373?

CVE-2026-4373 is a path traversal flaw in JetFormBuilder, Dynamic Blocks Form Builder. The product fails to canonicalize or restrict file paths supplied by a remote caller, so .. sequences or absolute paths reach restricted parts of the filesystem. Vendor description: The JetFormBuilder plugin for WordPress is vulnerable to arbitrary file read via path traversal in all versions up to, and including, 3.5.6.2. This is due to the 'Uploaded_File::set_from_array' method accepting user-supplied file paths from the Media Field preset JSON payload without validating that the path belongs to the WordPress uploads directory.

Why this CVE matters

Path traversal flaws look low-impact on paper but routinely chain into full compromise. An attacker who can read arbitrary files often pulls configuration secrets, session databases, or private keys, and many traversal bugs also allow writes that drop a webshell into the document root.

For deployments of JetFormBuilder, Dynamic Blocks Form Builder that have been exposed to the public internet during the disclosure window, the operating assumption should be that scanning has already happened. Even where exploitation has not been publicly observed, scanning for the vulnerable fingerprint is cheap and routine. Patching closes the door; log review and credential rotation close out the rest of the response.

Am I affected?

You are affected if your installation matches any of these version ranges:

Check your installed version against the list above. If you cannot determine the version, treat the system as affected and follow the upgrade path below.

Open JetFormBuilder, Dynamic Blocks Form Builder's About dialog or run the vendor-documented version-check command. Compare the result against the affected ranges in the advisory.

How to fix CVE-2026-4373

  1. Read the vendor advisory in full: https://www.wordfence.com/threat-intel/vulnerabilities/id/1801fd3e-d56f-4540-9700-9e9de8b465e1?source=cve
  2. Upgrade JetFormBuilder, Dynamic Blocks Form Builder to the patched build listed in the vendor advisory.
  3. Back up the configuration (and database, where applicable) before upgrading.
  4. Apply the patch in a maintenance window. For HA pairs, upgrade the standby node first, fail over, then upgrade the former primary.
  5. Restart the affected service so the patched binary loads, then verify the new version (see verification section).

Update the WordPress plugin via WP-CLI


# CVE-2026-4373 affects JetFormBuilder — Dynamic Blocks Form Builder 0 <= 3.5.6.2. Fixed in version 3.5.6.2.
# Vendor advisory: https://www.wordfence.com/threat-intel/vulnerabilities/id/1801fd3e-d56f-4540-9700-9e9de8b465e1?source=cve

# 1. Check the currently installed version of the plugin.
wp plugin get jetformbuilder --field=version

# 2. Update to the patched release named in the advisory.
wp plugin update jetformbuilder --version=3.5.6.2

# 3. Verify the update.
wp plugin get jetformbuilder --field=version
# The version must be >= 3.5.6.2 for the fix listed in the advisory.

# 4. If you cannot update right away, deactivate the plugin until you can.
wp plugin deactivate jetformbuilder


# Hosting-panel workflow (cPanel / Plesk / hosting dashboard):
# 1. WordPress -> Plugins -> Installed Plugins -> Update next to JetFormBuilder — Dynamic Blocks Form Builder.
# 2. Confirm the version under "Active Plugins" matches 3.5.6.2.


# Vendor advisory: https://www.wordfence.com/threat-intel/vulnerabilities/id/1801fd3e-d56f-4540-9700-9e9de8b465e1?source=cve
# Trigger an SSH-driven update from a Windows admin workstation.
ssh wpadmin@<host> "wp plugin update jetformbuilder --version=3.5.6.2"
ssh wpadmin@<host> "wp plugin get jetformbuilder --field=version"

Verify the fix landed


# CVE-2026-4373 verification checklist.

# 1. Confirm the running version matches 3.5.6.2 (replace the version probe with
#    the platform-specific command shown above).

# 2. Re-scan the host with your vulnerability scanner (Nessus, Qualys, Tenable,
#    OpenVAS, Wazuh). The scanner must no longer flag CVE-2026-4373.

# 3. Inspect recent service and kernel logs for crash-loops or rollback events.
journalctl -u <service-name> --since "10 minutes ago"
dmesg --since "10 minutes ago"

# 4. Cross-check the running build against the vendor advisory:
#    https://www.wordfence.com/threat-intel/vulnerabilities/id/1801fd3e-d56f-4540-9700-9e9de8b465e1?source=cve

If you cannot patch immediately

Block requests containing ../, ..%2f, or absolute path prefixes at a reverse proxy. Restrict access to the affected endpoint to trusted networks. Apply the patched build as the real fix.

How to verify the fix worked

If your installation was internet-reachable during the disclosure window, treat log review as part of the remediation rather than an optional follow-up. Look for unusually long URI paths containing traversal sequences, unexpectedly large responses from the affected endpoint, and outbound requests from the application to internal addresses or cloud-metadata endpoints. Treat any sensitive file the bug could disclose as exposed.

Frequently asked questions

Is CVE-2026-4373 being exploited in the wild?

Public exploitation has not been confirmed by CISA at the time of writing. Treat the patch as time-sensitive anyway; reports often lag actual abuse.

Will a WAF or IDS rule fully mitigate CVE-2026-4373?

No. Network-layer filters can reduce noise and slow opportunistic scanners, but they will not stop a determined attacker. The vendor patch is the only durable fix.

How long should I plan for the upgrade?

Typical vendor-documented upgrade windows for JetFormBuilder, Dynamic Blocks Form Builder run from a few minutes to under an hour depending on cluster size. Test in a staging environment first and follow the vendor's documented HA upgrade order.

References

*This guide was assembled from the official vendor advisory, the NVD record, and the CISA KEV catalog entry on 2026-05-25. Always confirm against the vendor advisory before applying changes in production.*