HomeWordPress vulnerabilitiesForminator Forms
Forminator Forms vulnerabilities
Forminator Forms has 54 known vulnerabilities in this database. The most recent published record is dated 7 Oct 2026.
- Known vulnerabilities
- 54
- Active installs
- 600,000+
- Latest version
- 1.57.3
- Last updated
- 17 Sep 2026
- Most recent
- 7 Oct 2026
Find it in your WordPress dashboard under Plugins. Severity is based on the CVSS score published with the CVE where one is available.
| Vulnerability | Severity | Affected | Fix | Published |
|---|---|---|---|---|
| Broken access control CVE-2026-96335 | High 7.5 | Up to 1.57.2 | Fixed in a later version (latest 1.57.3) | 6 h ago |
| Cross-site scripting (XSS) CVE-2026-92144 | High 7.2 | Up to 1.57.2 | Fixed in a later version (latest 1.57.3) | 6 d ago |
| Cross-site scripting (XSS) CVE-2026-85235 | High 7.2 | Up to 1.57.2 | Fixed in a later version (latest 1.57.3) | 6 d ago |
| Security weakness CVE-2026-87070 | Medium 5.3 | Before 1.57.2.1 | Fixed in 1.57.2.1 | 23 Sep 2026 |
| Security weakness CVE-2026-87071 | Medium 5.3 | Before 1.57.2.1 | Fixed in 1.57.2.1 | 23 Sep 2026 |
| Broken access control CVE-2026-87069 | Low 3.1 | Before 1.57.2.1 | Fixed in 1.57.2.1 | 23 Sep 2026 |
| Broken access control CVE-2026-87074 | Low 3.7 | Before 1.57.2.1 | Fixed in 1.57.2.1 | 23 Sep 2026 |
| Remote code execution CVE-2026-87067 | High 8.5 | Before 1.57.2.1 | Fixed in 1.57.2.1 | 20 Sep 2026 |
| Privilege escalation CVE-2026-87068 | Medium 6.6 | Before 1.57.2.1 | Fixed in 1.57.2.1 | 20 Sep 2026 |
| Remote code execution CVE-2026-92229 | Critical 9.1 | Up to 1.57.2 | Fixed in a later version (latest 1.57.3) | 19 Sep 2026 |
| Cross-site scripting (XSS) CVE-2026-18324 | High 7.2 | Up to 1.57.0.1 | Fixed in a later version (latest 1.57.3) | 28 Aug 2026 |
| Privilege escalation CVE-2026-19220 | Low 3.7 | Before 1.57.1 | Fixed in 1.57.1 | 26 Aug 2026 |
| Cross-site scripting (XSS) CVE-2026-18323 | High 7.2 | Up to 1.57.0.2 | Fixed in a later version (latest 1.57.3) | 25 Aug 2026 |
| Cross-site scripting (XSS) CVE-2026-18328 | High 7.2 | Up to 1.57.0 | Fixed in a later version (latest 1.57.3) | 25 Aug 2026 |
| Remote code execution CVE-2026-19221 | High 7.2 | Before 1.57.0.5 | Fixed in 1.57.0.5 | 22 Aug 2026 |
| Privilege escalation CVE-2026-19222 | Medium 6.6 | Before 1.57.0.7 | Fixed in 1.57.0.7 | 22 Aug 2026 |
| Remote code execution CVE-2026-15748 | Critical 9.8 | Up to 1.56.1 | Fixed in a later version (latest 1.57.3) | 18 Aug 2026 |
| Broken access control CVE-2026-12998 | Medium 5.3 | Up to 1.55.0.2 | Fixed in a later version (latest 1.57.3) | 16 Aug 2026 |
| Cross-site scripting (XSS) CVE-2026-18325 | High 7.2 | Up to 1.56.1 | Fixed in a later version (latest 1.57.3) | 6 Aug 2026 |
| Cross-site scripting (XSS) CVE-2026-57814 | High 7.1 | Up to 1.55.0.1 | Fixed in a later version (latest 1.57.3) | 13 Jul 2026 |
| Path traversal CVE-2026-57815 | High 7.5 | Up to 1.55.0.2 | Fixed in a later version (latest 1.57.3) | 13 Jul 2026 |
| Broken access control CVE-2026-6214 | Medium 6.5 | Up to 1.53.0 | Fixed in a later version (latest 1.57.3) | 7 May 2026 |
| Broken access control CVE-2026-6222 | Medium 5.3 | Up to 1.51.1 | Fixed in a later version (latest 1.57.3) | 7 May 2026 |
| Path traversal CVE-2026-5192 | High 7.5 | Up to 1.52.1 | Fixed in a later version (latest 1.57.3) | 5 May 2026 |
| Broken access control CVE-2026-2729 | Medium 5.3 | Up to 1.52.0 | Fixed in a later version (latest 1.57.3) | 5 May 2026 |
| Broken access control CVE-2026-32409 | Medium 5.3 | Up to 1.50.2 | Fixed in a later version (latest 1.57.3) | 13 Mar 2026 |
| Cross-site scripting (XSS) CVE-2026-2002 | Medium 4.4 | Up to 1.50.2 | Fixed in a later version (latest 1.57.3) | 17 Feb 2026 |
| Broken access control CVE-2025-14782 | Medium 5.3 | Up to 1.49.1 | Fixed in a later version (latest 1.57.3) | 9 Jan 2026 |
| SQL injection CVE-2025-7638 | Medium 4.9 | Up to 1.45.0 | Fixed in a later version (latest 1.57.3) | 18 Jul 2025 |
| PHP object injection CVE-2025-6464 | High 7.5 | Before 1.44.3 | Fixed in 1.44.3 | 2 Jul 2025 |
| Remote code execution CVE-2025-6463 | High 8.8 | Before 1.44.3 | Fixed in 1.44.3 | 2 Jul 2025 |
| Cross-site scripting (XSS) CVE-2025-5341 | Medium 6.4 | Before 1.44.2 | Fixed in 1.44.2 | 5 Jun 2025 |
| Security weakness CVE-2025-3479 | Medium 5.3 | Before 1.42.1 | Fixed in 1.42.1 | 17 Apr 2025 |
| Cross-site scripting (XSS) CVE-2025-3487 | Medium 6.4 | Before 1.42.1 | Fixed in 1.42.1 | 17 Apr 2025 |
| Cross-site scripting (XSS) CVE-2025-0469 | Medium 6.4 | Before 1.39.3 | Fixed in 1.39.3 | 27 Feb 2025 |
| Cross-site scripting (XSS) CVE-2024-7052 | Medium 4.8 | Before 1.38.3 | Fixed in 1.38.3 | 14 Feb 2025 |
| Cross-site scripting (XSS) CVE-2025-0470 | Medium 6.1 | Before 1.38.3 | Fixed in 1.38.3 | 31 Jan 2025 |
| Broken access control CVE-2024-9700 | Medium 5.3 | Before 1.36.1 | Fixed in 1.36.1 | 31 Oct 2024 |
| Broken access control CVE-2024-10402 | High 7.5 | Before 1.36.0 | Fixed in 1.36.0 | 26 Oct 2024 |
| Cross-site request forgery (CSRF) CVE-2024-9351 | Medium 4.3 | Before 1.36.0 | Fixed in 1.36.0 | 17 Oct 2024 |
| Cross-site request forgery (CSRF) CVE-2024-9352 | Medium 4.3 | Before 1.36.0 | Fixed in 1.36.0 | 17 Oct 2024 |
| Broken access control CVE-2024-7389 | High 7.5 | Before 1.29.2 | Fixed in 1.29.2 | 2 Aug 2024 |
| Cross-site scripting (XSS) CVE-2024-3053 | Medium 6.4 | Before 1.29.3 | Fixed in 1.29.3 | 9 Apr 2024 |
| Cross-site scripting (XSS) CVE-2024-1794 | High 7.2 | Up to 1.29.1 | Fixed in a later version (latest 1.57.3) | 9 Apr 2024 |
| Cross-site scripting (XSS) CVE-2024-29777 | High 7.1 | Before 1.29.1 | Fixed in 1.29.1 | 27 Mar 2024 |
| Cross-site scripting (XSS) CVE-2023-5119 | Medium 4.8 | Before 1.27.0 | Fixed in 1.27.0 | 20 Nov 2023 |
| Arbitrary file upload CVE-2023-6133 | Medium 6.6 | Up to 1.27.0 | Fixed in a later version (latest 1.57.3) | 15 Nov 2023 |
| Remote code execution CVE-2023-4596 | Critical 9.8 | Up to 1.24.6 | Fixed in a later version (latest 1.57.3) | 30 Aug 2023 |
| Cross-site scripting (XSS) CVE-2023-3134 | Medium 6.1 | Before 1.24.4 | Fixed in 1.24.4 | 31 Jul 2023 |
| Cross-site request forgery (CSRF) CVE-2021-4417 | Medium 5.4 | Before 1.13.5 | Fixed in 1.13.5 | 12 Jul 2023 |
| Security weakness CVE-2023-2010 | Low 3.1 | Before 1.24.1 | Fixed in 1.24.1 | 4 Jul 2023 |
| Cross-site scripting (XSS) CVE-2021-24700 | Medium 4.8 | Before 1.15.4 | Fixed in 1.15.4 | 23 Nov 2021 |
| Cross-site scripting (XSS) CVE-2019-9567 | Medium 6.1 | Before 1.6 | Fixed in 1.6 | 4 Mar 2019 |
| SQL injection CVE-2019-9568 | Medium 6.5 | Before 1.6 | Fixed in 1.6 | 4 Mar 2019 |
Read the published descriptions
- CVE-2026-96335, 7 Oct 2026
- Missing Authorization vulnerability in WPMU DEV Forminator allows Exploiting Incorrectly Configured Access Control Security Levels. This issue affects Forminator: from n/a through 1.57.2. CVE record
- CVE-2026-92144, 1 Oct 2026
- The Forminator Forms - Contact Form, Payment Form & Custom Form Builder plugin for WordPress is vulnerable to Stored Cross-Site Scripting via 'postdata-1[post-custom]' Parameter in all versions up to, and including, 1.57.2 due to insufficient input sanitization and output escaping. This makes it possible for unauthenticated attackers to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page. The required form submission nonce is freely obtainable by unauthenticated users via the publicly accessible wp_ajax_nopriv_forminator_get_nonce endpoint, making the full attack chain exploitable without any authentication or prior account. CVE record
- CVE-2026-85235, 1 Oct 2026
- The Forminator Forms - Contact Form, Payment Form & Custom Form Builder plugin for WordPress is vulnerable to Stored Cross-Site Scripting via Rich-Text Textarea Field in all versions up to, and including, 1.57.2 due to insufficient input sanitization and output escaping. This makes it possible for unauthenticated attackers to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page. Successful exploitation requires an administrator to open the stored submission entry in the Forminator Entries view and interact with the planted link, at which point WordPress core's jQuery-based click handler on `.contextual-help-tabs a` evaluates the entity-decoded href as HTML, firing the attacker's payload in the administrator's authenticated wp-admin session. CVE record
- CVE-2026-87070, 23 Sep 2026
- The Forminator Forms WordPress plugin before 1.57.2.1 does not verify that a request came from a trusted proxy before preferring client-supplied forwarding headers over the connecting address, and it uses that value both to enforce its per-visitor voting limit and to record who submitted an entry. Unauthenticated visitors can therefore vote without limit on any poll and can choose the address stored against every submission they make. CVE record
- CVE-2026-87071, 23 Sep 2026
- The Forminator Forms WordPress plugin before 1.57.2.1 does not restrict which metadata keys a form submission may supply, and does not exclude the keys WordPress reserves for its own use, so unauthenticated visitors submitting a public form that collects post content can attach metadata of their choosing to the post their submission creates. CVE record
- CVE-2026-87069, 23 Sep 2026
- The Forminator Forms WordPress plugin before 1.57.2.1 does not perform a nonce, capability or ownership check before running a one-time payment-field migration during the construction of one of its admin screens, and that construction happens on every wp-admin request for any logged-in user. Any authenticated user, including a Subscriber with no permissions in the Forminator Forms WordPress plugin before 1.57.2.1, can therefore rewrite the saved field configuration of any form on the site, including a live payment form. CVE record
- CVE-2026-87074, 23 Sep 2026
- The Forminator Forms WordPress plugin before 1.57.2.1 does not bind its saved-draft notification to the visitor who created the draft, and takes both the recipient address and the link written into the message from the request, so unauthenticated visitors can make the site send a message from its own mail configuration to any address, carrying a link of their choosing inside the site's own template. The token that authorises the send is handed to the anonymous caller by the Forminator Forms WordPress plugin before 1.57.2.1 itself and can be replayed without limit. CVE record
- CVE-2026-87067, 20 Sep 2026
- The Forminator Forms WordPress plugin before 1.57.2.1 does not restrict which classes may be instantiated when it deserialises a value taken from an XML-RPC request, allowing users who hold its forms-management permission to write a file of their choosing and execute arbitrary code. That permission belongs to an administrator by default, and to any role the site has granted it through the Forminator Forms WordPress plugin before 1.57.2.1's own settings, so the issue is reachable well below administrator on sites that use that feature. CVE record
- CVE-2026-87068, 20 Sep 2026
- The Forminator Forms WordPress plugin before 1.57.2.1 does not apply the role validation it enforces elsewhere when a registration form is nested inside an imported quiz, allowing a user who may import quizzes to publish a live, publicly reachable form that grants any role, including administrator, to anyone who submits it. The same user is refused an identical form through both the ordinary form editor and the ordinary form import. CVE record
- CVE-2026-92229, 19 Sep 2026
- The The Forminator Forms - Contact Form, Payment Form & Custom Form Builder plugin for WordPress is vulnerable to arbitrary shortcode execution in all versions up to, and including, 1.57.2. This is due to the software allowing users to execute an action that does not properly validate a value before running do_shortcode. This makes it possible for unauthenticated attackers to execute arbitrary shortcodes. CVE record
- CVE-2026-18324, 28 Aug 2026
- The Forminator Forms - Contact Form, Payment Form & Custom Form Builder plugin for WordPress is vulnerable to Stored Cross-Site Scripting via Rich-Text Textarea Field in all versions up to, and including, 1.57.0.1 due to insufficient input sanitization and output escaping. This makes it possible for unauthenticated attackers to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page. Exploitation requires that the targeted Textarea field has the Rich-Text editor option enabled. CVE record
- CVE-2026-19220, 26 Aug 2026
- The Forminator Forms WordPress plugin before 1.57.1 does not verify that site registration is enabled on the network before creating a site signup, allowing unauthenticated visitors to create a new site on a WordPress multisite network and gain administrator privileges on it. CVE record
- CVE-2026-18323, 25 Aug 2026
- The Forminator Forms - Contact Form, Payment Form & Custom Form Builder plugin for WordPress is vulnerable to Stored Cross-Site Scripting via Radio Field (Save and Continue Draft) in all versions up to, and including, 1.57.0.2 due to insufficient input sanitization and output escaping. This makes it possible for unauthenticated attackers to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page. This is exploitable because the Save-and-Continue draft submission AJAX endpoint is registered as nopriv, allowing unauthenticated attackers to bypass radio field option-membership validation and persist a crafted payload that, when rendered on the Submissions admin page, is auto-executed via the bundled Inputmask library's data-attribute callback binding. CVE record
- CVE-2026-18328, 25 Aug 2026
- The Forminator Forms - Contact Form, Payment Form & Custom Form Builder plugin for WordPress is vulnerable to DOM-Based Reflected Cross-Site Scripting via the 'error_description' parameter in all versions up to, and including, 1.57.0 due to insufficient input sanitization and output escaping. This makes it possible for unauthenticated attackers to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page. The vulnerability is only triggerable on pages hosting a Forminator form configured to use the Stripe Checkout Sessions payment API, which became the default in 1.56.0. CVE record
- CVE-2026-19221, 22 Aug 2026
- The Forminator Forms WordPress plugin before 1.57.0.5 does not restrict a network-wide setting to network administrators, allowing an administrator of any single site on a multisite network to execute arbitrary code across the entire network. CVE record
- CVE-2026-19222, 22 Aug 2026
- The Forminator Forms WordPress plugin before 1.57.0.7 does not consistently enforce the role restriction it applies to registration forms, allowing users who are permitted to build forms to configure one that assigns the administrator role to any visitor who registers through it. CVE record
- CVE-2026-15748, 18 Aug 2026
- The Forminator Forms plugin for WordPress is vulnerable to Arbitrary File Upload in all versions up to, and including, 1.56.1 via the handle_file_upload function. This is due to insufficient file type validation in handle_file_upload, where the dangerous-extension blocklist performs exact-key matching that is bypassed by pipe-alternative MIME type keys, combined with a public submission handler that trusts attacker-controlled upload field configuration injected via a forged Select field value. This makes it possible for unauthenticated attackers to upload files that may be executable, which makes remote code execution possible. CVE record
- CVE-2026-12998, 16 Aug 2026
- The Forminator Forms - Contact Form, Payment Form & Custom Form Builder plugin for WordPress is vulnerable to Insecure Direct Object Reference in all versions up to, and including, 1.55.0.2 via the 'draft' parameter due to missing validation on a user controlled key. This makes it possible for unauthenticated attackers to enumerate sequential integer entry IDs via the 'draft' parameter and read other users' saved draft form data, including names, email addresses, phone numbers, addresses, and free-form message content. This is only exploitable on forms that have the 'Save and Continue' feature enabled. CVE record
- CVE-2026-18325, 6 Aug 2026
- The Forminator Forms - Contact Form, Payment Form & Custom Form Builder plugin for WordPress is vulnerable to Stored Cross-Site Scripting via Forged Upload Record via Select Field in all versions up to, and including, 1.56.1 due to insufficient input sanitization and output escaping. This makes it possible for unauthenticated attackers to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page. The exploit is possible because Forminator_Core::sanitize_array() skips all filtering for keys prefixed with 'select-', and set_field_data() treats a submitted 'return' member as a trusted internal flag - allowing an unauthenticated attacker to forge and persist a complete upload field record with an arbitrary file_url value without any sanitization or validation. CVE record
- CVE-2026-57814, 13 Jul 2026
- Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') vulnerability in WPMU DEV - Your All-in-One WordPress Platform Forminator forminator allows DOM-Based XSS.This issue affects Forminator: from n/a through <= 1.55.0.1. CVE record
- CVE-2026-57815, 13 Jul 2026
- Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal') vulnerability in WPMU DEV - Your All-in-One WordPress Platform Forminator forminator allows Path Traversal.This issue affects Forminator: from n/a through <= 1.55.0.2. CVE record
- CVE-2026-6214, 7 May 2026
- The Forminator Forms plugin for WordPress is vulnerable to Missing Authorization in versions up to and including 1.53.0. This is due to the listen_for_saving_export_schedule() function in library/class-export.php failing to perform a capability check before saving the scheduled export configuration, unlike the parallel listen_for_csv_export() function which correctly verifies user permissions. This makes it possible for authenticated attackers with subscriber-level access to configure a scheduled export job that emails all form submissions to an attacker-controlled email address, resulting in sensitive data exfiltration. CVE record
- CVE-2026-6222, 7 May 2026
- The Forminator Forms plugin for WordPress is vulnerable to Missing Authorization in versions up to and including 1.51.1. This is due to the `processRequest()` method in `Forminator_Admin_Module_Edit_Page` (admin/abstracts/class-admin-module-edit-page.php) dispatching sensitive module-management actions - including export, delete, clone, delete-entries, publish/draft, and bulk variants - after only a nonce check, without ever verifying that the current user holds the `manage_forminator_modules` capability. The nonce used (`forminator_form_request`) is unconditionally embedded in the global `forminatorData` JavaScript object and localized on every Forminator admin page, including Templates and Reports pages accessible to users who explicitly lack module-management permissions. Because `processRequest()` is invoked during the `admin_menu` action hook - which fires before WordPress enforces page-level capability checks - a user whose Forminator role is restricted to Templates or Reports can craft a valid POST request targeting any published module and successfully trigger the vulnerable actions. This makes it possible for authenticated attackers with subscriber-level access (or any custom low-privilege Forminator role) to export the complete internal configuration of arbitrary forms/polls/quizzes (including notification routing, integration credentials, and conditional logic), delete modules, delete all submissions/votes, clone modules, or bulk-change publish/draft status. CVE record
- CVE-2026-5192, 5 May 2026
- 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. CVE record
- CVE-2026-2729, 5 May 2026
- The Forminator plugin for WordPress is vulnerable to authorization bypass in all versions up to, and including, 1.52.0. This is due to the plugin not properly verifying that a user is authorized to perform an action when processing attacker-supplied Stripe PaymentIntent identifiers in the public payment flow. This makes it possible for unauthenticated attackers to submit high-value paid forms as completed by reusing a previously succeeded low-value Stripe PaymentIntent, resulting in underpayment/payment bypass conditions. CVE record
- CVE-2026-32409, 13 Mar 2026
- Missing Authorization vulnerability in WPMU DEV - Your All-in-One WordPress Platform Forminator forminator allows Exploiting Incorrectly Configured Access Control Security Levels.This issue affects Forminator: from n/a through <= 1.50.2. CVE record
- CVE-2026-2002, 17 Feb 2026
- The Forminator Forms - Contact Form, Payment Form & Custom Form Builder plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the form_name parameter in all versions up to, and including, 1.50.2 due to insufficient input sanitization and output escaping. This makes it possible for authenticated attackers, with administrator-level access, to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page. The plugin allows admins to give form management permissions to lower level users, which could make this exploitable by users such as subscribers. CVE record
- CVE-2025-14782, 9 Jan 2026
- The Forminator Forms - Contact Form, Payment Form & Custom Form Builder plugin for WordPress is vulnerable to authorization bypass in all versions up to, and including, 1.49.1 via the 'listen_for_csv_export' function. This is due to the plugin not properly verifying that a user is authorized to perform an action. This makes it possible for authenticated attackers, with access to the Forminator dashboard, to export sensitive form submission data including personally identifiable information. CVE record
- CVE-2025-7638, 18 Jul 2025
- The Forminator Forms - Contact Form, Payment Form & Custom Form Builder plugin for WordPress is vulnerable to time-based SQL Injection via the `order_by` parameter in all versions up to, and including, 1.45.0 due to insufficient escaping on the user supplied parameter and lack of sufficient preparation on the existing SQL query. This makes it possible for authenticated attackers, with Administrator-level access and above, to append additional SQL queries into already existing queries that can be used to extract sensitive information from the database. CVE record
- CVE-2025-6464, 2 Jul 2025
- The Forminator Forms - Contact Form, Payment Form & Custom Form Builder plugin for WordPress is vulnerable to PHP Object Injection in all versions up to, and including, 1.44.2 via deserialization of untrusted input in the 'entry_delete_upload_files' function. This makes it possible for unauthenticated attackers to inject a PHP Object through a PHAR file. No known POP chain is present in the vulnerable software, which means this vulnerability has no impact unless another plugin or theme containing a POP chain is installed on the site. If a POP chain is present via an additional plugin or theme installed on the target system, it may allow the attacker to perform actions like delete arbitrary files, retrieve sensitive data, or execute code depending on the POP chain present. Deserialization occurs when the form submission is deleted, whether by an Administrator or via auto-deletion determined by plugin settings. CVE record
- CVE-2025-6463, 2 Jul 2025
- The Forminator Forms - Contact Form, Payment Form & Custom Form Builder plugin for WordPress is vulnerable to arbitrary file deletion due to insufficient file path validation in the 'entry_delete_upload_files' function in all versions up to, and including, 1.44.2. This makes it possible for unauthenticated attackers to include arbitrary file paths in a form submission. The file will be deleted when the form submission is deleted, whether by an Administrator or via auto-deletion determined by plugin settings. This can easily lead to remote code execution when the right file is deleted (such as wp-config.php). CVE record
- CVE-2025-5341, 5 Jun 2025
- The Forminator Forms - Contact Form, Payment Form & Custom Form Builder plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the ‘id' and 'data-size’ parameters in all versions up to, and including, 1.44.1 due to insufficient input sanitization and output escaping. This makes it possible for authenticated attackers, with Contributor-level access and above, to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page. CVE record
- CVE-2025-3479, 17 Apr 2025
- The Forminator Forms - Contact Form, Payment Form & Custom Form Builder plugin for WordPress is vulnerable to Order Replay in all versions up to, and including, 1.42.0 via the 'handle_stripe_single' function due to insufficient validation on a user controlled key. This makes it possible for unauthenticated attackers to reuse a single Stripe PaymentIntent for multiple transactions. Only the first transaction is processed via Stripe, but the plugin sends a successful email message for each transaction, which may trick an administrator into fulfilling each order. CVE record
- CVE-2025-3487, 17 Apr 2025
- The Forminator Forms - Contact Form, Payment Form & Custom Form Builder plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the ‘limit’ parameter in all versions up to, and including, 1.42.0 due to insufficient input sanitization and output escaping. This makes it possible for authenticated attackers, with Contributor-level access and above, to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page. CVE record
- CVE-2025-0469, 27 Feb 2025
- The Forminator Forms - Contact Form, Payment Form & Custom Form Builder plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the slider template data in all versions up to, and including, 1.39.2 due to insufficient input sanitization and output escaping. This makes it possible for authenticated attackers, with Contributor-level access and above, to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page. CVE record
- CVE-2024-7052, 14 Feb 2025
- The Forminator Forms WordPress plugin before 1.38.3 does not sanitise and escape some of its settings, which could allow high privilege users such as Admin to perform Stored Cross-Site Scripting attacks even when the unfiltered_html capability is disallowed (for example in multisite setup) CVE record
- CVE-2025-0470, 31 Jan 2025
- The Forminator Forms - Contact Form, Payment Form & Custom Form Builder plugin for WordPress is vulnerable to Reflected Cross-Site Scripting via the title parameter in all versions up to, and including, 1.38.2 due to insufficient input sanitization and output escaping. This makes it possible for unauthenticated attackers to inject arbitrary web scripts in pages that execute if they can successfully trick a user into performing an action such as clicking on a link. CVE record
- CVE-2024-9700, 31 Oct 2024
- The Forminator Forms - Contact Form, Payment Form & Custom Form Builder plugin for WordPress is vulnerable to Insecure Direct Object Reference in all versions up to, and including, 1.36.0 via the submit_quizzes() function due to missing validation on the 'entry_id' user controlled key. This makes it possible for unauthenticated attackers to modify other user's quiz submissions. CVE record
- CVE-2024-10402, 26 Oct 2024
- The Forminator Forms - Contact Form, Payment Form & Custom Form Builder plugin for WordPress is vulnerable to unauthorized access due to a missing capability check on a function in all versions up to, and including, 1.35.1. This makes it possible for authenticated attackers, with Contributor-level access and above, and permissions granted by an Administrator, to create new or edit existing forms, including updating the default registration role to Administrator on User Registration forms. CVE record
- CVE-2024-9351, 17 Oct 2024
- The Forminator Forms - Contact Form, Payment Form & Custom Form Builder plugin for WordPress is vulnerable to Cross-Site Request Forgery in all versions up to, and including, 1.35.1. This is due to missing or incorrect nonce validation on the quiz 'create_module' function. This makes it possible for unauthenticated attackers to create draft quizzes via a forged request granted they can trick a site administrator into performing an action such as clicking on a link. CVE record
- CVE-2024-9352, 17 Oct 2024
- The Forminator Forms - Contact Form, Payment Form & Custom Form Builder plugin for WordPress is vulnerable to Cross-Site Request Forgery in all versions up to, and including, 1.35.1. This is due to missing or incorrect nonce validation on the custom form 'create_module' function. This makes it possible for unauthenticated attackers to create draft forms via a forged request granted they can trick a site administrator into performing an action such as clicking on a link. CVE record
- CVE-2024-7389, 2 Aug 2024
- The Forminator plugin for WordPress is vulnerable to Sensitive Information Exposure in all versions up to, and including, 1.29.1 via class-forminator-addon-hubspot-wp-api.php. This makes it possible for unauthenticated attackers to extract the HubSpot integration developer API key and make unauthorized changes to the plugin's HubSpot integration or expose personally identifiable information from plugin users using the HubSpot integration. CVE record
- CVE-2024-3053, 9 Apr 2024
- The Forminator - Contact Form, Payment Form & Custom Form Builder plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the ‘id’ forminator_form shortcode attribute in versions up to, and including, 1.29.2 due to insufficient input sanitization and output escaping. This makes it possible for authenticated attackers, with contributor-level permissions and above, to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page. CVE record
- CVE-2024-1794, 9 Apr 2024
- The Forminator plugin for WordPress is vulnerable to Stored Cross-Site Scripting via an uploaded file (e.g. 3gpp file) in all versions up to, and including, 1.29.0 due to insufficient input sanitization and output escaping. This makes it possible for unauthenticated attackers to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page. CVE record
- CVE-2024-29777, 27 Mar 2024
- Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') vulnerability in WPMU DEV - Your All-in-One WordPress Platform Forminator forminator.This issue affects Forminator: from n/a through <= 1.29.0. CVE record
- CVE-2023-5119, 20 Nov 2023
- The Forminator WordPress plugin before 1.27.0 does not properly sanitize the redirect-url field in the form submission settings, which could allow high-privilege users such as an administrator to inject arbitrary web scripts even when the unfiltered_html capability is disallowed (for example in a multisite setup). CVE record
- CVE-2023-6133, 15 Nov 2023
- The Forminator plugin for WordPress is vulnerable to arbitrary file uploads due to insufficient blacklisting on the 'forminator_allowed_mime_types' function in versions up to, and including, 1.27.0. This makes it possible for authenticated attackers with administrator-level capabilities or above to upload arbitrary files on the affected site's server, but due to the htaccess configuration, remote code cannot be executed. CVE record
- CVE-2023-4596, 30 Aug 2023
- The Forminator plugin for WordPress is vulnerable to arbitrary file uploads due to file type validation occurring after a file has been uploaded to the server in the upload_post_image() function in versions up to, and including, 1.24.6. This makes it possible for unauthenticated attackers to upload arbitrary files on the affected site's server which may make remote code execution possible. CVE record
- CVE-2023-3134, 31 Jul 2023
- The Forminator WordPress plugin before 1.24.4 does not properly escape values that are being reflected inside form fields that use pre-populated query parameters, which could lead to reflected XSS attacks. CVE record
- CVE-2021-4417, 12 Jul 2023
- The Forminator - Contact Form, Payment Form & Custom Form Builder plugin for WordPress is vulnerable to Cross-Site Request Forgery in versions up to, and including, 1.13.4. This is due to missing or incorrect nonce validation on the listen_for_saving_export_schedule() function. This makes it possible for unauthenticated attackers to export form submissions via a forged request granted they can trick a site administrator into performing an action such as clicking on a link. CVE record
- CVE-2023-2010, 4 Jul 2023
- The Forminator WordPress plugin before 1.24.1 does not use an atomic operation to check whether a user has already voted, and then update that information. This leads to a Race Condition that may allow a single user to vote multiple times on a poll. CVE record
- CVE-2021-24700, 23 Nov 2021
- The Forminator WordPress plugin before 1.15.4 does not sanitize and escape the email field label, which could allow high privilege users to perform Cross-Site Scripting attacks even when the unfiltered_html is disallowed CVE record
- CVE-2019-9567, 4 Mar 2019
- The "Forminator Contact Form, Poll & Quiz Builder" plugin before 1.6 for WordPress has XSS via a custom input field of a poll. CVE record
- CVE-2019-9568, 4 Mar 2019
- The "Forminator Contact Form, Poll & Quiz Builder" plugin before 1.6 for WordPress has SQL Injection via the wp-admin/admin.php?page=forminator-entries entry[] parameter if the attacker has the delete permission. CVE record
What to do if you run Forminator Forms
If you run Forminator Forms, open WordPress and check the installed version in Plugins. Compare it with the affected versions in the vulnerability record. If a fixed version is available, take a current backup and update to that version or the latest supported release.
If no fixed version exists, consider disabling and removing the plugin or replacing it with a maintained alternative. After dealing with the affected software, check administrator users, unexpected file changes, redirects, unfamiliar pages and security logs for signs that the site may already have been altered.
Email me about new Forminator Forms vulnerabilities
Free. We email you when a new vulnerability is published for Forminator Forms, usually within minutes. Confirm by email; unsubscribe any time.
Focus on your business. We’ll take care of your website.
From everyday updates to ongoing care, we keep your website working.