CVE-2026-119632 — Wpmudev Forminator Forms – Contact Form, Payment Form & Custom Form Builder
HIGHCVE-2026-119632 is a high-severity (CVSS 7.2) Cross-site Scripting (XSS) vulnerability in wpmudev Forminator Forms – Contact Form, Payment Form & Custom Form Builder. Versions up to 1.58.4 are affected; the records list no fixed version yet, so check the vendor advisory below.
The Forminator Forms – Contact Form, Payment Form & Custom Form Builder plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the 'textarea-N (rich-text draft value,…
Description
The Forminator Forms – Contact Form, Payment Form & Custom Form Builder plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the 'textarea-N (rich-text draft value, saved as Save-and-Continue draft meta)' parameter in all versions up to, and including, 1.58.4 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 requires the targeted form to have a Rich-Text Textarea field with Save-and-Continue enabled and public submission permissions — once a crafted draft is saved, the payload executes whenever any user, including an administrator, resumes the draft or opens the Draft ID link from the Forminator Submissions screen.
Affected Products
Forminator Forms – Contact Form, Payment Form & Custom Form BuilderwpmudevDetection & mitigation playbook
Vendor / applianceDetect
Inventory every wpmudev Forminator Forms – Contact Form, Payment Form & Custom Form Builder deployment and check each version against the affected-products list above.
Remediation status
The records we use list no fixed version for CVE-2026-119632 (versions up to 1.58.4 are affected). Check the wpmudev Forminator Forms – Contact Form, Payment Form & Custom Form Builder advisory for a patched release, and apply the workarounds below until you can upgrade.
Mitigate without a patch
Escape or sanitise the affected output on the server side rather than relying on client-side filtering, and add a Content-Security-Policy that blocks inline script execution so injected markup cannot run even if it reaches the page. Alongside that, restrict the management interface to trusted networks and apply the vendor's recommended configuration mitigations.
Frequently Asked Questions
Is CVE-2026-119632 being exploited in your environment?
Detect and block the exploit chain at execution, on systems you cannot patch yet.