dbcve.org
Improper Input ValidationWeakness · CWE-20

CVE-2026-15288

HIGH · 7.5 CVSS v3.1 Published 2026-07-10
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
84/100
Remediation priority · High
Remotely reachable No privileges Zero-click 6 weeks old

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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 summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

The SureForms WordPress plugin accepts payment amounts directly from user-controlled POST data in the create_payment_intent and create_subscription_intent functions without validating against the form's configured price. This allows unauthenticated attackers to submit arbitrary payment values, purchasing goods/services at reduced prices.

MitigationImplement server-side validation in the affected functions to ensure the submitted payment amount matches the form's configured price before processing any Stripe payment intent.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
High
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Confirm SureForms plugin installation
    In WordPress admin, go to Plugins > Installed Plugins and locate SureForms, or check the plugin version via wp-content/plugins/sureforms/readme.txt
    Affected if SureForms plugin is installed and active
  2. Identify installed SureForms version
    Check the plugin version number from the WordPress plugins page or the plugin header in wp-content/plugins/sureforms/sureforms.php
    Affected if Installed version falls within the vulnerable version range (if known) or is an unpatched release
  3. Verify Stripe payment functionality is enabled
    Review SureForms settings and check if any forms are configured to accept payments via Stripe integration (look for payment-enabled forms or Stripe connection settings)
    Affected if Stripe payment processing is enabled and forms are configured to accept payments
  4. Inspect payment intent functions for missing validation
    Examine the plugin source code in the create_payment_intent and create_subscription_intent functions; verify if POST parameters (e.g., amount, price, payment_amount) are used directly without server-side validation against the form's configured price
    Affected if The functions accept and process payment values from POST data without validating they match the form's configured price
  5. Check for server-side price validation
    Review the payment processing logic to determine if there is code that compares the submitted payment amount to the form's stored/configured price before creating the Stripe payment intent
    Affected if No server-side validation exists to ensure submitted payment amount equals the configured form price

A user is affected if SureForms is installed with Stripe payment functionality enabled and the payment intent functions accept POST data values without server-side validation against the configured form price.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Implement server-side validation in the affected functions to ensure the submitted payment amount matches the form's configured price before processing any Stripe payment intent.

Recommended fix Moderate confidence

Update to version 2.2.2 or later (check wordpress.org for the latest stable release)

  1. 1. Navigate to the WordPress admin dashboard
  2. 2. Go to Plugins > Installed Plugins
  3. 3. Locate SureForms – Drag and Drop Form Builder for WordPress
  4. 4. Check if an update is available and update to the latest version
  5. 5. Alternatively, download the latest version from wordpress.org/plugins/sureforms/ and upload via Plugins > Add New > Upload Plugin
  6. 6. Verify the update was successful and test payment forms to confirm the fix

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation3.0 h
  • Testing2.0 h
  • Review / QA1.0 h
8.0 hours of engineering $1,420
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,272.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-15288 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-15288 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data