CVE-2026-7792
MediumCVSS 5.3Exploitation Probability (EPSS)
Low risk10th percentile - higher than 10% of all known CVEs
Summary
The WPForms plugin for WordPress up to version 1.10.0.1 does not properly verify the authenticity of PayPal Commerce webhooks. Unauthenticated attackers can forge webhook events and modify payment records, e.g., reactivate a cancelled subscription.
Risk Assessment
An attacker can manipulate subscription statuses, potentially leading to unauthorized access to paid content or financial loss.
Recommendation
Immediately update the plugin to a version that verifies PayPal webhook HMAC-SHA256 signatures.
Other vulnerabilities in WPForms
See all- CVE-2026-15782Medium
WPForms plugin for WordPress up to 2.0.0.1 has a Stored XSS vulnerability via the data-sitekey attribute of OptinMonster integration. Authenticated attackers with contributor-level access can inject scripts that execute on page view.
- CVE-2026-12127Medium
The WPForms plugin for WordPress up to version 1.10.2 is vulnerable to CRLF Injection, allowing email header injection. The flaw occurs due to improper handling of the Reply-To display name, enabling unauthenticated attackers to inject arbitrary headers like Bcc into outgoing notification emails.
- CVE-2026-48835High
In WPForms versions <= 1.10.0.4, there is an issue with unauthenticated access to the contact form, leading to broken access control.
- CVE-2026-4986Medium
The WPForms WordPress plugin before version 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.
Original NVD description (English source)
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.