Website support, maintenance and fixes for UK businessesCall 0208 088 8371info@websupportservices.co.uk

HomeWordPress vulnerabilitiesWPForms

WPForms vulnerabilities

WPForms has 14 known vulnerabilities in this database. The most recent published record is dated 25 Sep 2026.

Known vulnerabilities
14
Active installs
5m+
Latest version
2.0.2.1
Last updated
23 Sep 2026
Most recent
25 Sep 2026

Find it in your WordPress dashboard under Plugins. Severity is based on the CVSS score published with the CVE where one is available.

VulnerabilitySeverityAffectedFixPublished
Cross-site scripting (XSS)
CVE-2026-88996
Medium 6.1Up to 2.0.2Fixed in a later version (latest 2.0.2.1)12 d ago
Broken access control
CVE-2026-74991
Medium 6.8Before 2.0.2Fixed in 2.0.213 d ago
Cross-site scripting (XSS)
CVE-2026-15782
Medium 4.9Up to 2.0.0.1Fixed in a later version (latest 2.0.2.1)21 Jul 2026
Security weakness
CVE-2026-12127
Medium 5.3Up to 1.10.2Fixed in a later version (latest 2.0.2.1)1 Jul 2026
Broken access control
CVE-2026-4986
Medium 5.3Before 1.10.0.5Fixed in 1.10.0.59 Jun 2026
Security weakness
CVE-2026-7792
Medium 5.3Up to 1.10.0.1Fixed in a later version (latest 2.0.2.1)6 Jun 2026
Cross-site scripting (XSS)
CVE-2025-3794
Medium 5.4Up to 1.9.5Fixed in a later version (latest 2.0.2.1)9 May 2025
Cross-site scripting (XSS)
CVE-2024-13403
Medium 6.4Before 1.9.3.2Fixed in 1.9.3.24 Feb 2025
Cross-site scripting (XSS)
CVE-2024-11223
Medium 4.7Before 1.9.2.3Fixed in 1.9.2.326 Dec 2024
Broken access control
CVE-2024-11205
High 8.5Before 1.9.2.2Fixed in 1.9.2.210 Dec 2024
Cross-site scripting (XSS)
CVE-2024-7056
Low 3.5Before 1.9.1.6Fixed in 1.9.1.625 Nov 2024
Cross-site request forgery (CSRF)
CVE-2024-10593
Medium 4.3Before 1.9.2.1Fixed in 1.9.2.113 Nov 2024
Security weakness
CVE-2024-3649
Medium 5.3Up to 1.8.7.2Fixed in a later version (latest 2.0.2.1)2 May 2024
Cross-site scripting (XSS)
CVE-2020-10385
Medium 5.4Before 1.5.9Fixed in 1.5.924 Mar 2020
Read the published descriptions
CVE-2026-88996, 25 Sep 2026
The WPForms - AI Form Builder for WordPress - Contact Forms, Payment Forms, Survey Form, Quiz & More plugin for WordPress is vulnerable to Reflected Cross-Site Scripting via 'page_title' POST Parameter via {page_title} Smart Tag in all versions up to, and including, 2.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 execute if they can successfully trick a user into performing an action such as clicking on a link. This is only exploitable on forms whose admin-authored confirmation message places the {page_title} Smart Tag inside an HTML attribute context. CVE record
CVE-2026-74991, 24 Sep 2026
The WPForms WordPress plugin before 2.0.2 does not verify that a Stripe payment object supplied during a public form submission belongs to it before acting on it, allowing unauthenticated users to trigger a full refund and an immediate subscription cancellation against payments created by other applications on the site owner's Stripe account. CVE record
CVE-2026-15782, 21 Jul 2026
The WPForms - AI Form Builder for WordPress - Contact Forms, Payment Forms, Survey Form, Quiz & More plugin for WordPress is vulnerable to Stored Cross-Site Scripting via OptinMonster Integration data-sitekey Attribute in Post Content in all versions up to, and including, 2.0.0.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. Exploitation requires the OptinMonster plugin to be installed and configured with an active inline campaign that outputs matching #om-{id} markup on the target page, as the WPForms handler only fires when OptinMonster emits its 'om.Campaign.load' event. CVE record
CVE-2026-12127, 1 Jul 2026
The WPForms - Easy Form Builder for WordPress - Contact Forms, Payment Forms, Surveys, & More plugin for WordPress is vulnerable to Improper Neutralization of CRLF Sequences ('CRLF Injection') in all versions up to, and including, 1.10.2 This is due to `get_reply_to_address()` processing the Reply-To display name through smart-tag expansion with context `'notification'` instead of `'notification-reply-to'`, which bypasses email-address validation while `wpforms_sanitize_textarea_field()` intentionally preserves CR/LF characters that are never stripped before the display name is concatenated into the raw `Reply-To:` mail header string. This makes it possible for unauthenticated attackers to inject arbitrary additional email headers - such as `Bcc:` - into outgoing notification emails, silently blind-copying all notification email copies to an attacker-controlled address. Exploitation requires that a form notification is configured to use a Paragraph Text (textarea) field as the Reply-To display name via a Smart Tag. CVE record
CVE-2026-4986, 9 Jun 2026
The WPForms WordPress plugin before 1.10.0.5 does not verify the authenticity of incoming PayPal webhook events before processing them, allowing unauthenticated attackers to forge webhook payloads and manipulate the payment state of arbitrary transactions. CVE record
CVE-2026-7792, 6 Jun 2026
The WPForms - Easy Form Builder for WordPress - Contact Forms, Payment Forms, Surveys, & More plugin for WordPress is vulnerable to Insufficient Verification of Data Authenticity in versions up to and including 1.10.0.1. This is due to the PayPal Commerce webhook endpoint processing unauthenticated JSON webhook payloads without verifying that the request originated from PayPal using the required HMAC-SHA256 webhook signature, and only checking whether the supplied event_type is whitelisted before dispatching the attacker-controlled resource data to handlers that update payment records. This makes it possible for unauthenticated attackers who know a valid PayPal subscription_id to forge PayPal webhook events and modify subscription payment records, such as reactivating a cancelled or suspended subscription by setting its subscription_status to active. CVE record
CVE-2025-3794, 9 May 2025
The WPForms - Easy Form Builder for WordPress - Contact Forms, Payment Forms, Surveys, & More plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the start_timestamp parameter in all versions up to, and including, 1.9.5 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-13403, 4 Feb 2025
The WPForms - Easy Form Builder for WordPress - Contact Forms, Payment Forms, Surveys, & More plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the ‘fieldHTML’ parameter in all versions up to, and including, 1.9.3.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-2024-11223, 26 Dec 2024
The WPForms WordPress plugin before 1.9.2.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-2024-11205, 10 Dec 2024
The WPForms plugin for WordPress is vulnerable to unauthorized modification of data due to a missing capability check on the 'wpforms_is_admin_page' function in versions starting from 1.8.4 up to, and including, 1.9.2.1. This makes it possible for authenticated attackers, with Subscriber-level access and above, to refund payments and cancel subscriptions. CVE record
CVE-2024-7056, 25 Nov 2024
The WPForms WordPress plugin before 1.9.1.6 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-2024-10593, 13 Nov 2024
The WPForms - Easy Form Builder for WordPress - Contact Forms, Payment Forms, Surveys, & More plugin for WordPress is vulnerable to Cross-Site Request Forgery in all versions up to, and including, 1.9.1.6. This is due to missing or incorrect nonce validation on the process_admin_ui function. This makes it possible for unauthenticated attackers to delete WPForm logs 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-3649, 2 May 2024
The Contact Form by WPForms - Drag & Drop Form Builder for WordPress plugin for WordPress is vulnerable to price manipulation in versions up to, and including, 1.8.7.2. This is due to a lack of controls on several product parameters. This makes it possible for unauthenticated attackers to manipulate prices, product information, and quantities for purchases made via the Stripe payment integration. CVE record
CVE-2020-10385, 24 Mar 2020
A stored cross-site scripting (XSS) vulnerability exists in the WPForms Contact Form (aka wpforms-lite) plugin before 1.5.9 for WordPress. CVE record

What to do if you run WPForms

If you run WPForms, 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 WPForms vulnerabilities

Free. We email you when a new vulnerability is published for WPForms, 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.

Get website support