CVE-2026-15288

SureForms – Drag and Drop Form Builder for WordPress <= 2.2.1 - Unauthenticated Stripe Payment Amount Manipulation

2026-02-13 18:17
andrea bocchetti

Strategic Overview

Status
Patched in 2.2.2
Affected Plugin
SureForms – Contact Form Builder, AI Forms, Payment Form, Survey & Quiz
Affected Version
<= 2.2.1
CVSS
7.5High
Weakness type
CWE-20 · Improper Input Validation
CVE
CVE-2026-15288
View all SureForms – Contact Form Builder, AI Forms, Payment Form, Survey & Quiz vulnerabilities

At a glance

CVE-2026-15288 is a high-severity Improper Input Validation vulnerability in the SureForms WordPress plugin, affecting versions <= 2.2.1. It carries a CVSS score of 7.5 (reachable over the network; low attack complexity; high integrity impact). Exploitation requires no authentication. The issue is fixed in version 2.2.2; sites on affected versions should update now. Disclosed February 2026, reported by andrea bocchetti.

Vulnerability Overview

The SureForms – Drag and Drop Form Builder for WordPress plugin for WordPress is vulnerable to Improper Input Validation in all versions up to, and including, 2.2.1. This is due to the plugin accepting the payment amount directly from user-controlled POST data in the 'create_payment_intent' and 'create_subscription_intent' functions without validating it against the form's configured price. This makes it possible for unauthenticated attackers to modify the payment amount to any arbitrary value when submitting a Stripe payment form, potentially purchasing products or services at significantly reduced prices.

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. A successful exploit has high impact on integrity.

CWE-20: Improper Input Validation

SureForms <= 2.2.1 carries this weakness at create_payment_intent, and reaching it takes no account at all. Improper input validation means the application accepts input without confirming it has the form, type or range the code downstream assumes.

The concrete impact depends on where the unvalidated value lands, which is why records in this class range from cosmetic bugs to full compromise. For SureForms the fix is 2.2.2: builds <= 2.2.1 are affected, anything from 2.2.2 onward is not.

Remediation

Update to version 2.2.2, or a newer patched version

How does WordSec protect against this?

Requests carrying this pattern arrive without a session, so nothing upstream of the firewall gets a chance to reject them: WordSec's web application firewall inspects request payloads before WordPress loads them. None of that substitutes for the fix: SureForms 2.2.2 closes this, and updating the plugin is the step that ends it.

  • Firewall
  • Login Security
  • Alerts

External References

https://www.cve.org/CVERecord?id=CVE-2026-15288https://www.wordfence.com/threat-intel/vulnerabilities/id/8b0e0f22-de42-4da9-a0c1-ae41ba57be03https://nvd.nist.gov/vuln/detail/CVE-2026-15288

Related records

Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C