Summary
A Stored Cross-Site Scripting (XSS) vulnerability affects the Forminator Forms plugin. This vulnerability impacts all versions of the plugin up to and including 1.58.4. The issue is patched in version 1.58.5. 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 1.58.4 and earlier; fixed in 1.58.5
Is my site vulnerable?
To determine if your WordPress site uses a vulnerable version of the Forminator Forms plugin, you can check the installed version through your WordPress administration panel or by inspecting your site's file system.
Via WordPress Admin Panel:
Log in to your WordPress dashboard.
Navigate to the "Plugins" menu item.
Locate "Forminator Forms – Contact Form, Payment Form & Custom Form Builder" in the list of installed plugins.
The version number is displayed next to the plugin name. If this version is 1.58.4 or earlier, your site is vulnerable.
Via File System (FTP/SFTP or File Manager):
Connect to your site's server using an FTP/SFTP client or your hosting provider's file manager.
Navigate to the
wp-content/plugins/forminatordirectory.Open the
forminator.phpfile (or a similar main plugin file) in a text editor.Look for a line containing
Version:near the top of the file. The number following this indicates the installed plugin version. If this version is 1.58.4 or earlier, your site is vulnerable.
If your site runs Forminator Forms version 1.58.4 or earlier, it is exposed to this Stored Cross-Site Scripting vulnerability.
What an attacker actually does
An unauthenticated attacker can inject malicious web scripts into a WordPress site running a vulnerable version of the Forminator Forms plugin. This attack targets forms configured with specific settings. The vulnerability stems from insufficient input sanitization and output escaping within the plugin, specifically concerning the textarea-N parameter, which handles rich-text draft values saved as "Save-and-Continue" draft meta.
To execute this attack, the targeted form must include a Rich-Text Textarea field. This field must have the "Save-and-Continue" feature enabled, and the form itself must allow public submissions. The attacker crafts a malicious payload, typically a JavaScript snippet, and submits it as a draft through this specially configured form. The plugin then stores this crafted draft data, including the malicious script, within the site's database.
Once the malicious draft is saved, the injected script remains dormant until a user interacts with it. The payload executes whenever any user, including an administrator, attempts to resume the crafted draft. The script also executes if a user opens the Draft ID link directly from the Forminator Submissions screen within the WordPress admin area. Successful exploitation can lead to various negative outcomes, such as session hijacking, unauthorized data access, website defacement, or redirection of users to malicious sites.
How to detect a compromise
Detecting a compromise related to this Stored Cross-Site Scripting vulnerability involves examining the Forminator Forms plugin's data for unusual or unexpected script injections. Since the vulnerability involves data stored as "Save-and-Continue" drafts, the primary area of concern is the WordPress database.
Indicators of compromise may include:
Unexpected script execution: Users, particularly administrators, report seeing unusual pop-ups, redirects, or changes in page content when resuming Forminator drafts or viewing draft IDs.
Unusual entries in form submissions/drafts: Reviewing Forminator's submission and draft records in the WordPress admin area might reveal entries with suspicious content in rich-text fields, especially those containing HTML tags like
<script>or event handlers likeonerror,onload, etc.
To investigate programmatically, you can query the WordPress database directly for suspicious content within the postmeta table, where Forminator draft data is often stored. You will look for _forminator_form_draft_ related meta keys.
A WP-CLI command can help search for potentially malicious script tags within the wp_postmeta table. Replace wp_ with your actual database prefix if it differs.
wp db query "SELECT meta_value FROM wp_postmeta WHERE meta_key LIKE '_forminator_form_draft_%' AND meta_value LIKE '%<script>%' LIMIT 10;"This command searches for meta_value entries associated with Forminator form drafts that contain the <script> tag. Review the output for any unexpected or malicious-looking JavaScript. Keep in mind that legitimate form content might contain some HTML, so context is important. Look for full script blocks or suspicious attributes.
Additionally, you can search for other common XSS payload components:
wp db query "SELECT meta_value FROM wp_postmeta WHERE meta_key LIKE '_forminator_form_draft_%' AND (meta_value LIKE '%onmouseover=%' OR meta_value LIKE '%onerror=%' OR meta_value LIKE '%javascript:%') LIMIT 10;"If you find suspicious entries, it indicates a potential compromise or an attempted attack. Further investigation into the specific draft content and the user who created it may be necessary.
How to fix
To address the CVE-2026-119632 vulnerability in Forminator Forms, follow these steps:
Update the Plugin: The primary fix is to update the Forminator Forms – Contact Form, Payment Form & Custom Form Builder plugin to a patched version.
Update to Forminator Forms version 1.58.5 or later. Version 1.58.6, released shortly after, includes "Security hardening" which further addresses security concerns.
Access your WordPress dashboard, navigate to "Plugins", and locate Forminator Forms. Click "Update Now" if an update is available. If no update option appears, manually update the plugin.
Clear Caches: After updating, clear any website caching mechanisms you have in place (e.g., caching plugins, server-side caches, CDN caches) to ensure the updated code is served to all users.
Review and Clean Existing Drafts (if compromised): If you suspect your site was compromised before updating, review existing Forminator drafts for malicious content.
Navigate to the Forminator Submissions screen in your WordPress admin area.
Carefully inspect draft entries, especially those for forms with Rich-Text Textarea fields and "Save-and-Continue" enabled.
Delete any drafts that contain suspicious script tags or other malicious code.
Mitigation (if immediate update is not possible): If you cannot update the plugin immediately, you can implement a temporary mitigation:
For any publicly accessible forms that use a Rich-Text Textarea field, disable the "Save-and-Continue" option. This removes the specific attack vector for this vulnerability. Re-enable this feature only after updating the plugin to a patched version.
Regularly updating all WordPress plugins, themes, and the core WordPress installation is a fundamental security practice.
Timeline
Date | Event |
|---|---|
2026-11-09 | Version 1.58.5 released |
2026-11-16 | Version 1.58.6 released |
2026-11-21 | CVE published |