Summary
A privilege escalation vulnerability exists in the Forminator Forms plugin. This affects sites running Forminator Forms – Contact Form, Payment Form & Custom Form Builder versions before 1.58.4. A patch is available in version 1.58.4. There is no evidence of active exploitation for this vulnerability.
Affected and patched versions
Forminator Forms – Contact Form, Payment Form & Custom Form Builder (plugin forminator): affected before 1.58.4; fixed in 1.58.4
Is my site vulnerable?
To determine if your WordPress site is affected by CVE-2026-111579, you need to check the version of the Forminator Forms plugin installed. This process involves accessing your WordPress administration dashboard.
Log in to your WordPress site as an administrator. In the left-hand navigation menu, locate and click on "Plugins". This will take you to the list of all installed plugins on your site. Scroll through the list to find "Forminator Forms – Contact Form, Payment Form & Custom Form Builder".
Next to the plugin's name, you will see its currently installed version number. If the displayed version is earlier than 1.58.4, your site is running a vulnerable version of the plugin. For example, versions such as 1.58.3, 1.57.0, or any other version number lower than 1.58.4 indicates a vulnerable installation. If your site shows version 1.58.4 or a higher version number, the vulnerability has been addressed in your installation.
It is important to verify the version directly from your WordPress dashboard. Relying on cached information or external tools might not always provide the most current status of your specific installation.
What an attacker actually does
CVE-2026-111579 describes a privilege escalation vulnerability within the Forminator Forms plugin. This issue stems from insufficient restrictions on the capabilities a user may grant themselves through specific configurations of the plugin's forms. An unauthenticated attacker can exploit this weakness to bypass payment requirements on user registration forms, subsequently gaining elevated privileges on the affected WordPress site.
The attack scenario involves a payment-gated user registration form created with Forminator Forms. If the payment gateway configured for this specific form is initially connected and then later disconnected, a flaw in the plugin's logic emerges. Unauthenticated visitors can then complete the user registration form without making the required payment. Upon successful submission, the system assigns the user role configured for that form to the newly registered account. This assigned role could be as high as an administrator, granting the attacker full control over the WordPress site.
This vulnerability does not require the attacker to have any prior authentication or special permissions on the site. The ability to register an account with an elevated role, such as an administrator, without fulfilling the payment condition, represents a significant security risk. The core problem lies in how the plugin handles user role assignment and payment verification when a payment gateway is no longer active for a form that was previously configured to require payment for registration.
How to detect a compromise
Detecting a compromise related to CVE-2026-111579 primarily involves identifying unauthorized user accounts with elevated privileges. Since this vulnerability allows unauthenticated users to register with potentially high-level roles, the focus should be on reviewing user accounts and their associated permissions.
One of the most direct indicators of compromise is the presence of new, unexpected user accounts, particularly those assigned administrator or editor roles, that you do not recognize. Regularly review the list of users on your WordPress site. Navigate to "Users" > "All Users" in your WordPress administration dashboard. Look for any accounts that were recently created and appear suspicious. Pay close attention to usernames, email addresses, and registration dates that do not align with legitimate user activity.
For sites with a large number of users or those that experience frequent legitimate registrations, a more systematic approach may be necessary. If your site maintains user registration logs, examine these for any entries that indicate registrations bypassing payment requirements or originating from unusual IP addresses.
You can also use WP-CLI, the command-line interface for WordPress, to inspect user accounts. To list all users and their roles, you can execute the following command in your site's root directory:
wp user list --fields=ID,user_login,user_email,user_registered,roles --format=tableThis command provides a table of user IDs, usernames, email addresses, registration dates, and assigned roles. Review this output for any recently registered users with administrator or other high-privilege roles that you did not authorize.
To specifically check for administrator accounts, you can refine the command:
wp user list --role=administrator --fields=ID,user_login,user_email,user_registered --format=tableThis will list only users with the administrator role. Cross-reference these accounts with your known legitimate administrators. Any unfamiliar administrator account, especially one with a recent registration date, should be investigated immediately. If you find such an account, it is a strong indicator of potential compromise.
Additionally, if you have security logging plugins installed, review their logs for unusual login attempts, user creation events, or changes to user roles. These logs can provide further context and help pinpoint the exact time and source of any unauthorized activity.
How to fix
Addressing CVE-2026-111579 involves updating the Forminator Forms plugin and conducting a security review of your WordPress site. Follow these steps to mitigate the vulnerability and respond to any potential compromise:
Update the Forminator Forms plugin: The primary fix for this vulnerability is to update your Forminator Forms plugin to version 1.58.4 or higher.
Log in to your WordPress administration dashboard.
Navigate to "Plugins" > "Installed Plugins".
Locate "Forminator Forms – Contact Form, Payment Form & Custom Form Builder" in the list.
If an update is available, you will see a notice beneath the plugin name. Click the "Update Now" link to install the latest version.
If the plugin is already at version 1.58.4 or higher, no further action is needed regarding the patch.
Review user accounts: After updating the plugin, it is crucial to review all user accounts on your site for any unauthorized additions or privilege changes.
Go to "Users" > "All Users" in your WordPress dashboard.
Carefully examine the list for any unfamiliar usernames, email addresses, or accounts with administrator or other high-level roles that you did not create or authorize.
If you identify any suspicious accounts, delete them immediately. Before deleting, consider changing their role to "None" or "Subscriber" temporarily to prevent immediate re-login, then proceed with deletion.
If an unauthorized administrator account was created, deleting it is a critical step.
Reset passwords for legitimate administrators: As a precautionary measure, have all legitimate administrators and users with high-level roles change their passwords. This helps ensure that any compromised credentials are no longer valid.
Verify Forminator form configurations: Review any User Registration forms created with Forminator, especially those that were previously configured with payment gateways. Ensure that payment gateways are correctly set up if payments are required, or that the forms are configured to assign appropriate roles for free registrations.
Implement additional security measures: Consider implementing a robust security plugin that offers features such as two-factor authentication, activity logging, and file integrity monitoring. These tools can provide an additional layer of defense and help detect future unauthorized activity.
Timeline
Date | Event |
|---|---|
2026-10-29 | Patch release |
2026-11-09 | WPScan details published |
2026-11-10 | NVD record published |
2026-11-11 | NVD record last modified |
2026-11-11 | Dr. Web report |