CVE-2026-4373 HIGH

CVE-2026-4373: JetFormBuilder <= 3.5.6.2 - Unauthenticated Arbitrary File Read via Media Field

Vendor Jetmonsters
Product JetFormBuilder — Dynamic Blocks Form Builder
Weakness CWE-36
Published March 21, 2026
Last update April 8, 2026

CVSS base score

7.5/10
Attack vector Network
Attack complexity Low
Privileges required None
User interaction None
Confidentiality High
Integrity None

CVSS vector

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N

What the vulnerability does

01Description

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. Combined with an insufficient same-file check in 'File_Tools::is_same_file' that only compares basenames, this makes it possible for unauthenticated attackers to exfiltrate arbitrary local files as email attachments by submitting a crafted form request when the form is configured with a Media Field and a Send Email action with file attachment.

Explanation of Vulnerability in Simple Terms

02Summary

JetFormBuilder versions up to 3.5.6.2 contain a path traversal vulnerability that allows unauthenticated attackers to read sensitive files from the server. The vulnerability requires no user interaction and can be exploited over the network. An attacker can access files outside the intended directory structure, potentially exposing configuration files, database credentials, or other sensitive data.

What an attacker can do

03Attacker Capabilities

Read arbitrary files from the server without authentication.

Potential impact on your site

04Site Impact

Sensitive files (config, credentials, private data) may be exposed to unauthenticated attackers.

Conditions required to exploit

05Prerequisites

Network access to the affected JetFormBuilder installation; no authentication or user interaction required.

Key dates

06Disclosure timeline

March 21, 2026 CVE published
April 8, 2026 Record updated