dbcve.org
Improper Input ValidationWeakness · CWE-20

CVE-2026-4987

HIGH · 7.5 CVSS v3.1 Published 2026-03-28
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

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 – Contact Form, Payment Form & Other Custom Form Builder plugin for WordPress is vulnerable to Payment Amount Bypass in all versions up to, and including, 2.5.2. This is due to the create_payment_intent() function performing a payment validation solely based on the value of a user-controlled parameter. This makes it possible for unauthenticated attackers to bypass configured form payment-amount validation and create underpriced payment/subscription intents by setting form_id to 0.

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 has a payment validation bypass vulnerability in the create_payment_intent() function. The function validates payment amounts using a user-controlled parameter rather than retrieving the configured amount from the form's stored settings. By setting form_id to 0, unauthenticated attackers can bypass this validation and create payment intents with arbitrary (typically minimal) amounts, resulting in financial loss.

MitigationUpdate to version 2.5.3 or later which implements server-side payment amount validation that retrieves amounts from trusted form configuration rather than trusting user-supplied values. Until patched, monitor for anomalous low-value payment transactions.

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. Verify SureForms plugin is installed
    In WordPress admin, go to Plugins > Installed Plugins and look for SureForms, or check the filesystem at wp-content/plugins/sureforms for the plugin directory
    Affected if The plugin is present and active
  2. Check installed SureForms version
    In WordPress admin Plugins page, click on the plugin to view details and note the version number, or read the main plugin file header
    Affected if Version is lower than 2.5.3 (the patched release)
  3. Identify active payment forms
    Review SureForms forms that have payment/stripe integration enabled. Check form settings for any payment-related fields or Stripe integration toggles
    Affected if Any payment-enabled forms exist in the environment
  4. Monitor for anomalous payment amounts
    Review payment transaction logs from Stripe dashboard or plugin payment records for unusually low amounts (such as $0.01 or $1) that deviate from expected product/service pricing
    Affected if Transactions exist with minimal amounts that do not match configured product prices
  5. Inspect for form_id=0 requests
    Check web server access logs and WordPress debug logs for POST requests to the create_payment_intent endpoint containing form_id=0 parameter
    Affected if Requests with form_id=0 are observed in logs

A user is affected if the SureForms plugin version is below 2.5.3 AND payment forms are configured, particularly if low-value transactions or form_id=0 requests are observed.

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

Update to version 2.5.3 or later which implements server-side payment amount validation that retrieves amounts from trusted form configuration rather than trusting user-supplied values. Until patched, monitor for anomalous low-value payment transactions.

Recommended fix High confidence

Version 2.5.3 or later

  1. Log in to the WordPress admin dashboard
  2. Navigate to Plugins > Installed Plugins
  3. Find SureForms in the plugin list
  4. Check if the current version is 2.5.2 or below
  5. If vulnerable, click 'Update Now' to install the latest version
  6. Verify the update was successful and the plugin is now running version 2.5.3 or higher

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

Have this fixed Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,860
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-4987 — 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-4987 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