Forminator Forms – Contact Form, Payment Form & Custom Form Builder

Forminator through 1.57.1 exposes an affected operation without authentication. An unauthenticated request can change protected plugin or site state, producing limited integrity impact.

Forminator through 1.57.0.1 does not adequately sanitize and escape submissions to a Textarea field with the Rich-Text editor enabled. An unauthenticated submitter can store script that executes when a user views the affected submission or page.

Forminator before 1.57.1 creates multisite signups without checking whether network site registration is enabled. An unauthenticated visitor can create a new site on the WordPress multisite network and gain Administrator privileges on that site.

Forminator through 1.57.0 lets an unauthenticated attacker supply script-capable error_description input that reaches a DOM rendering path without adequate sanitization or escaping. The issue is reachable on pages containing a Forminator form configured for the Stripe Checkout Sessions payment API, which became the default in 1.56.0.

Forminator through 1.57.0.2 exposes its Save-and-Continue draft submission AJAX path to unauthenticated users. An attacker can bypass radio-field option membership validation and persist a crafted value; the bundled Inputmask library binds the stored data attribute as a callback when an administrator opens the submission in the Submissions screen, executing script in that privileged session.

Forminator <= 1.57.0 allows an unauthenticated attacker to place attacker-controlled serialized data into an unsafe PHP deserialization path. Practical code execution depends on a usable gadget chain, but the CNA assigns high confidentiality, integrity and availability impact.

Forminator Forms through 1.56.1 lets an unauthenticated attacker forge a Select field value so the public submission handler trusts attacker-controlled upload-field configuration. The handle_file_upload() dangerous-extension blocklist performs exact-key matching and can be bypassed with pipe-alternative MIME type keys, allowing files that may be executable to reach the upload operation and potentially produce remote code execution.

Forminator through 1.55.0.2 does not verify ownership of the draft key supplied to forms using Save and Continue. An unauthenticated attacker can enumerate sequential integer IDs in the draft parameter and retrieve other users' saved form data, including names, email addresses, phone numbers, addresses, and free-form messages. Only forms with Save and Continue enabled are affected. The public.

An unauthenticated visitor can submit attacker-controlled content that Forminator 1.56.0 and earlier renders without sufficient output encoding.

A user with Contributor access can cross an authorization boundary in Forminator 1.56.0 and earlier and obtain elevated WordPress privileges. Version 1.56.0.1 is recorded as unaffected.

Forminator through 1.56.1 allows an unauthenticated caller to submit crafted data through the public custom-form action, including wp_ajax_nopriv_forminator_submit_form_custom-forms. Forminator_Core::sanitize_array() skips filtering for keys beginning select-, and set_field_data() trusts a client-supplied return flag as though it came from internal plugin logic. An attacker can therefore persist a forged upload-field record containing an arbitrary nested file.file_url. Forminator_Form_Entry_Model later inserts that URL unescaped into an upload link, producing stored XSS when the affected entry is rendered. The disclosed path forges metadata; it does not establish an arbitrary file upload. The exact nested POST representation, required form configuration and victim-facing entry view are not disclosed.

Forminator is affected by filesystem traversal. Exposure depends on how the affected operation is made reachable by the site. A crafted path can escape the intended directory and reach files or directories elsewhere on the server. The published affected range is <= 1.55.0.2.

Forminator is affected by cross-site scripting. Exposure depends on how the affected operation is made reachable by the site. Injected script can execute in the affected site's origin when the vulnerable output is viewed. The published affected range is <= 1.55.0.1.

Forminator is affected by cross-site scripting. The vulnerable path is reachable without authentication. Injected script can execute in the affected site's origin when the vulnerable output is viewed. The published affected range is n/a through 1.53.1.

Forminator Forms – Contact Form, Payment Form & Custom Form Builder is affected by a security weakness. Exploitation requires an authenticated subscriber account. The resulting impact depends on how the affected component exposes the vulnerable operation. The published affected range is <= 1.53.0.

Forminator Forms – Contact Form, Payment Form & Custom Form Builder is affected by a security weakness. Exploitation requires an authenticated subscriber account. The resulting impact depends on how the affected component exposes the vulnerable operation. The published affected range is <= 1.51.1.

Forminator Forms – Contact Form, Payment Form & Custom Form Builder is affected by a security weakness. The vulnerable path is reachable without authentication. The resulting impact depends on how the affected component exposes the vulnerable operation. The published affected range is <= 1.52.0.

Forminator is affected by a security weakness. Exposure depends on how the affected operation is made reachable by the site. The resulting impact depends on how the affected component exposes the vulnerable operation.

Forminator Forms – Contact Form, Payment Form & Custom Form Builder is affected by SQL injection. Exploitation requires an authenticated administrator account. A successful request can alter database queries and expose or modify WordPress data.

Forminator Forms – Contact Form, Payment Form & Custom Form Builder is affected by code execution. The vulnerable path is reachable without authentication. Successful exploitation can run attacker-controlled code in the WordPress hosting account.

Forminator Forms – Contact Form, Payment Form & Custom Form Builder is affected by code execution. The vulnerable path is reachable without authentication. Successful exploitation can run attacker-controlled code in the WordPress hosting account.

Forminator Forms – Contact Form, Payment Form & Custom Form Builder is affected by cross-site scripting. Exploitation requires an authenticated contributor account. Injected script can execute in the affected site's origin when the vulnerable output is viewed.

Forminator Forms – Contact Form, Payment Form & Custom Form Builder is affected by cross-site scripting. Exploitation requires an authenticated contributor account. Injected script can execute in the affected site's origin when the vulnerable output is viewed.

Forminator Forms – Contact Form, Payment Form & Custom Form Builder is affected by a security weakness. The vulnerable path is reachable without authentication. The resulting impact depends on how the affected component exposes the vulnerable operation.

Forminator Forms – Contact Form, Payment Form & Custom Form Builder is affected by cross-site scripting. Exploitation requires an authenticated contributor account. Injected script can execute in the affected site's origin when the vulnerable output is viewed.

Forminator Forms – Contact Form, Payment Form & Custom Form Builder is affected by cross-site scripting. The vulnerable path is reachable without authentication. Injected script can execute in the affected site's origin when the vulnerable output is viewed.

Forminator Forms – Contact Form, Payment Form & Custom Form Builder is affected by broken access control. The vulnerable path is reachable without authentication. A successful request can reach data or an operation that should be restricted to another user or a more privileged role.

Forminator Forms – Contact Form, Payment Form & Custom Form Builder is affected by cross-site request forgery. The vulnerable path is reachable without authentication. Exploitation relies on a signed-in privileged user submitting an attacker-controlled request.

Forminator Forms – Contact Form, Payment Form & Custom Form Builder is affected by cross-site request forgery. The vulnerable path is reachable without authentication. Exploitation relies on a signed-in privileged user submitting an attacker-controlled request.

Forminator is affected by cross-site scripting. Exposure depends on how the affected operation is made reachable by the site. Injected script can execute in the affected site's origin when the vulnerable output is viewed.

Forminator is affected by sensitive information exposure. The vulnerable path is reachable without authentication. Successful exploitation can disclose data that should not be available to the caller.

Forminator is affected by cross-site scripting. Exposure depends on how the affected operation is made reachable by the site. Injected script can execute in the affected site's origin when the vulnerable output is viewed.

Forminator is affected by SQL injection. Exploitation requires an authenticated WordPress account. A successful request can alter database queries and expose or modify WordPress data.

Forminator is affected by dangerous file upload. Exposure depends on how the affected operation is made reachable by the site. Successful exploitation can place attacker-controlled executable content on the server and may lead to full site compromise.

Forminator – Contact Form, Payment Form & Custom Form Builder is affected by cross-site scripting. Exploitation requires an authenticated contributor account. Injected script can execute in the affected site's origin when the vulnerable output is viewed.

Forminator is affected by cross-site scripting. The vulnerable path is reachable without authentication. Injected script can execute in the affected site's origin when the vulnerable output is viewed.

Forminator is affected by cross-site scripting. Exposure depends on how the affected operation is made reachable by the site. Injected script can execute in the affected site's origin when the vulnerable output is viewed.

Forminator is affected by a security weakness. Exposure depends on how the affected operation is made reachable by the site. The resulting impact depends on how the affected component exposes the vulnerable operation.

Forminator is affected by dangerous file upload. Exploitation requires an authenticated administrator account. Successful exploitation can place attacker-controlled executable content on the server and may lead to full site compromise.

Forminator is affected by dangerous file upload. The vulnerable path is reachable without authentication. Successful exploitation can place attacker-controlled executable content on the server and may lead to full site compromise.

Forminator is affected by cross-site scripting. Exposure depends on how the affected operation is made reachable by the site. Injected script can execute in the affected site's origin when the vulnerable output is viewed.

Forminator – Contact Form, Payment Form & Custom Form Builder is affected by cross-site request forgery. The vulnerable path is reachable without authentication. Exploitation relies on a signed-in privileged user submitting an attacker-controlled request.

Forminator is affected by a security weakness. Exposure depends on how the affected operation is made reachable by the site. The resulting impact depends on how the affected component exposes the vulnerable operation.

Forminator is affected by cross-site scripting. Exposure depends on how the affected operation is made reachable by the site. Injected script can execute in the affected site's origin when the vulnerable output is viewed.

Forminator is affected by cross-site scripting. Exposure depends on how the affected operation is made reachable by the site. Injected script can execute in the affected site's origin when the vulnerable output is viewed.

Forminator is affected by SQL injection. Exposure depends on how the affected operation is made reachable by the site. A successful request can alter database queries and expose or modify WordPress data.

Forminator is affected by cross-site scripting. Exposure depends on how the affected operation is made reachable by the site. Injected script can execute in the affected site's origin when the vulnerable output is viewed.