WPForms – AI Form Builder for WordPress – Contact Forms, Payment Forms, Survey Form, Quiz & More 1.10.0.1 - 2.0.2.1 - Unauthenticated Payment Bypass on Paid Forms
Strategic Overview
- Status
- Patched in 2.0.2.2
- Affected Plugin
- WPForms – AI Form Builder for WordPress – Contact Forms, Payment Forms, Survey Form, Quiz & More
- Affected Version
1.10.0.1 – 2.0.2.1- CVSS
- 5.3Medium
- Weakness type
- CWE-602 · Client-Side Enforcement of Server-Side Security
- CVE
CVE-2026-82844
At a glance
CVE-2026-82844 is a medium-severity Client-Side Enforcement of Server-Side Security vulnerability in the WPForms WordPress plugin, affecting versions 1.10.0.1 – 2.0.2.1. It carries a CVSS score of 5.3 (reachable over the network; low attack complexity). Exploitation requires no authentication. The issue is fixed in version 2.0.2.2; sites on affected versions should update now. Disclosed October 2026, reported by Abdulrhman Mari.
Vulnerability Overview
The WPForms – AI Form Builder for WordPress – Contact Forms, Payment Forms, Survey Form, Quiz & More plugin for WordPress is vulnerable to Payment Bypass in versions 1.10.0.1 through 2.0.2.1. This is due to missing server-side enforcement that blocks submission when no PayPal payment identifier is present, and a conditional check that allowed form errors to be suppressed when the PayPal Commerce field was not marked required in the form builder. This makes it possible for unauthenticated attackers to submit a PayPal Commerce payment form without completing payment, receiving the form confirmation and notification emails without any order existing at PayPal. A form must have a PayPal Commerce payment field.
Technical Analysis
The vector marks this flaw as remotely reachable over the network, with low attack complexity — no special timing or configuration is needed, and no privileges on the target site, and no interaction from a victim user.
CWE-602: Client-Side Enforcement of Server-Side Security
The product is composed of a server that relies on the client to implement a mechanism that is intended to protect the server.
Remediation
Update to version 2.0.2.2, or a newer patched version
How does WordSec protect against this?
This one needs no account at all, which puts it outside what login hardening can reach; WordSec's login security narrows the account-level paths around it, and the firewall is what inspects the request itself. None of that substitutes for the fix: WPForms 2.0.2.2 closes this, and updating the plugin is the step that ends it.
- Login Security
- Alerts
External References
Related records
Same weakness class
Other vulnerabilities in WPForms – AI Form Builder for WordPress – Contact Forms, Payment Forms, Survey Form, Quiz & More
- 8.5CVE-2024-11205: WPForms 1.8.4 - 1.9.2.1 Authenticated (Subscriber+)
CVE-2024-11205 - 7.2Contact Form by WPForms <= 1.6.0.1 Cross-Site Scripting
- 7.1Contact Form by WPForms <= 1.4.8 Reflected Cross-Site Scripting
- 6.8Contact Form by WPForms <= 1.7.5.3 Arbitrary File Access
- 6.5CVE-2026-84744: WPForms Lite 1.5.0.1… Arbitrary Shortcode Execution
CVE-2026-84744 - 6.4CVE-2024-13403: WPForms Lite <= 1.9.3.1 Stored Cross-Site Scripting
CVE-2024-13403 - 6.4CVE-2020-10385: Contact Form by WPForms <= 1.5.8.2 Stored XSS
CVE-2020-10385 - 6.4Contact Form by WPForms Stored XSS
Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C