CVE-2026-5192 HIGH

CVE-2026-5192: Forminator Forms – Contact Form, Payment Form & Custom Form Builder <= 1.52.1 - Unauthenticated Arbitrary File Read via 'upload-1[file][file_path]'

Vendor Wpmudev
Product Forminator Forms – Contact Form, Payment Form & Custom Form Builder
Weakness CWE-22 · Path traversal
Published May 5, 2026
Last update May 5, 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 Forminator Forms – Contact Form, Payment Form & Custom Form Builder plugin for WordPress is vulnerable to Path Traversal in versions up to, and including, 1.52.1 via the 'upload-1[file][file_path]' parameter. This makes it possible for unauthenticated attackers to read the contents of arbitrary files on the server, which can contain sensitive information. Successful exploitation requires a publicly accessible form with a File Upload field where Save and Continue is enabled in that form's Behavior settings and the Save and Continue email notification is configured to attach uploaded files in Email Notifications.

Explanation of Vulnerability in Simple Terms

02Summary

Forminator Forms versions up to 1.52.1 contain a path traversal vulnerability that allows unauthenticated attackers to read arbitrary files from the server. An attacker can craft a malicious request to access sensitive files outside the intended directory, such as configuration files or database credentials. No user interaction is required. Update to a version newer than 1.52.1 to resolve this issue.

What an attacker can do

03Attacker Capabilities

Read arbitrary files from your server, including configuration and credential files.

Potential impact on your site

04Site Impact

Sensitive files like wp-config.php or database credentials could be exposed to attackers.

Conditions required to exploit

05Prerequisites

Network access only; no authentication or user interaction required.

Key dates

06Disclosure timeline

May 5, 2026 CVE published
May 5, 2026 Record updated