Forminator Forms – Contact Form, Payment Form & Custom Form Builder plugin for WordPress versions up to and including 1.58.1 is vulnerable to arbitrary shortcode execution. This vulnerability allows unauthenticated attackers to execute arbitrary shortcodes via a crafted GET request to the search results page or by submitting an anonymous comment on posts with comments enabled. No specific Forminator content or configuration is required to exploit this issue.
Forminator Forms plugin for WordPress versions up to 1.58.1 is vulnerable to arbitrary shortcode execution due to improper handling of user-controlled input in notification templates. This vulnerability allows unauthenticated attackers to execute arbitrary WordPress shortcodes by submitting crafted quiz data. The impact depends on other installed plugins and themes that register shortcodes, potentially leading to content injection or information disclosure.
The Broken Link Checker WordPress plugin up to version 2.4.14.1 contains a code injection vulnerability (CWE-94) that allows unauthenticated attackers to execute arbitrary shortcodes. This occurs because the plugin does not properly validate input before calling do_shortcode. Exploitation requires that a malicious shortcode payload be submitted in a comment and approved through normal moderation, after which the shortcode executes automatically via WP-Cron.
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.
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.
Forminator Forms – Contact Form, Payment Form & Custom Form Builder plugin for WordPress versions up to and including 1.57.2 contains a critical vulnerability that allows unauthenticated attackers to execute arbitrary shortcodes. This occurs due to improper validation before invoking the do_shortcode function, leading to potential code injection.
The Hummingbird – Speed Optimization, Caching, Minify, Compress & CDN plugin for WordPress is vulnerable to Remote Code Execution in all versions up to, and including, 3.21.0 via the log_msg() function in core/modules/class-page-cache.php. The page-cache debug log is written to wp-content/wphb-logs/page-caching-log.php, a directly web-accessible PHP file that is supposed to be protected by a leading '<?php die(); ?>' header. That header is guarded by class_exists( 'Filesystem' ), which can never match because class_exists() resolves string arguments in the global namespace while the class is Hummingbird\Core\Filesystem; when the log is created during a front-end request the header is therefore omitted entirely. get_cookies() then writes the raw name of any cookie matching the wphb_cache_ prefix into that file without sanitization. This makes it possible for unauthenticated attackers to write arbitrary PHP into the log file with a single anonymous request and execute it by requesting the file directly, resulting in full remote code execution. Exploitation requires the site administrator to have enabled Page Caching with the Debug Log option (non-default), and the log file to be created during a front-end request — a state reached by the plugin's own 'Clear logs' action, any cache flush, or unattended via the plugin's daily log-rotation cron, which can strip the protective header from an existing log file.
The Broken Link Checker plugin for WordPress is vulnerable to Stored Cross-Site Scripting via Comment Author URL / Link Log in all versions up to, and including, 2.4.13 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 an administrator to perform the plugin's standard dismiss-and-recheck workflow on a link submitted by the attacker via the WordPress comment author URL field, after which the attacker's HTTP server issues a redirect to a URL containing an HTML/JavaScript payload that is stored verbatim in the link log.
The WPMU DEV Dashboard WordPress plugin contains an authentication bypass vulnerability in all versions up to and including 5.0.1. This flaw arises from inconsistent HMAC message construction between two AJAX actions, allowing an attacker to replay a valid HMAC and gain administrator access on sites with Hub SSO enabled and mapped to an admin. The vulnerability has a critical severity with a CVSS score of 9.8.
The Forminator Forms plugin for WordPress contains a stored cross-site scripting (XSS) vulnerability in its Rich-Text Textarea Field. This vulnerability affects all versions up to and including 1.57.0.1 and allows unauthenticated attackers to inject malicious scripts that execute when users access the affected pages. Exploitation requires the Rich-Text editor option to be enabled on the targeted Textarea field.
CVE-2026-18328 is a DOM-Based Reflected Cross-Site Scripting (XSS) vulnerability in the Forminator Forms plugin for WordPress. It affects all versions up to and including 1.57.0. The issue arises from insufficient input sanitization and output escaping of the 'error_description' parameter on pages hosting a Forminator form configured to use the Stripe Checkout Sessions payment API, which became the default in version 1.56.0. This vulnerability allows unauthenticated attackers to inject arbitrary scripts that execute when a user accesses the affected page.
The Forminator Forms plugin for WordPress is affected by a stored cross-site scripting (XSS) vulnerability in all versions up to and including 1.57.0.2. This vulnerability allows unauthenticated attackers to inject malicious scripts via the radio field in the Save and Continue Draft feature. The injected scripts execute when a user views the affected submissions page in the admin interface. The vulnerability arises from insufficient input sanitization and output escaping, combined with an AJAX endpoint accessible without authentication.
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.
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.
The WPMU DEV Dashboard plugin for WordPress contains an authentication bypass vulnerability in all versions up to and including 5.0.0. This flaw allows unauthenticated attackers to perform privileged actions such as installing and activating plugins from attacker-supplied URLs, deleting plugins and themes, upgrading WordPress core, or logging in as an administrator via SSO. The vulnerability arises because sites not connected to the WPMU DEV Hub have an empty API key, making request signatures trivially forgeable. Version 5.0.0 also removed a replay check, increasing exploitability. Sites connected to a WPMU DEV account with a valid API key are not affected.
Forminator Forms plugin for WordPress versions up to and including 1.56.1 contains a stored cross-site scripting (XSS) vulnerability. This flaw allows unauthenticated attackers to inject malicious scripts via a forged upload record in a select field, due to improper input sanitization and output escaping. The vulnerability arises because certain input keys bypass filtering and a submitted internal flag is trusted without validation. Exploited scripts execute when users access affected pages.
The Branda plugin for WordPress is vulnerable to privilege escalation via account takeover in all versions up to, and including, 3.4.29. This is due to the plugin not properly validating a user's identity prior to updating their password. This makes it possible for unauthenticated attackers to change arbitrary user's passwords, including administrators, and leverage that to gain access to their account.
CVE-2026-6214 is a medium severity vulnerability in the Forminator Forms WordPress plugin up to version 1.53.0. It involves missing authorization checks in the listen_for_saving_export_schedule() function, allowing authenticated users with subscriber-level access to configure scheduled export jobs. This can lead to sensitive form submission data being emailed to attacker-controlled addresses. The vulnerability does not affect availability or integrity but impacts confidentiality. No official patch or remediation guidance is currently confirmed. No known exploits are reported in the wild.
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.
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.