dbcve.org
VulnerabilityAwaiting classification

CVE-2026-11567

MEDIUM · 5.9 CVSS v3.1 Published 2026-07-14
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
68/100
Remediation priority · Elevated
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 WordPress plugin before 2.11.1 does not properly validate the payment amount on forms that use a dynamically-sourced (variable/hidden) payment amount, allowing unauthenticated users to underpay for the configured product or subscription. Forms using a fixed configured price are not affected.

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 before 2.11.1 fails to server-side validate payment amounts for forms using dynamically-sourced (variable/hidden) payment fields. Attackers can manipulate these hidden fields to send reduced payment amounts, allowing purchase of products or subscriptions at underpriced levels. Forms with fixed configured prices are unaffected.

MitigationUpdate SureForms to version 2.11.1 or later. Additionally, implement server-side validation that verifies payment amounts against trusted backend price data rather than trusting client-submitted values for all form submissions.

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
High
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
High
Availability
None

CVSS:3.1/AV:N/AC:H/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 version
    In WordPress admin, go to Plugins > Installed Plugins and locate SureForms. Check the version number listed there. Alternatively, check the plugin file header in wp-content/plugins/sureforms/bsf-core/class-bsf-core.php or the main plugin file.
    Affected if The installed version is earlier than 2.11.1 (e.g., 2.10.0, 2.9.5, etc.)
  2. Identify forms with payment fields
    In SureForms builder, review each form that contains payment-related fields. Look specifically for fields where the payment amount is set to 'Dynamic' or 'Variable' source, or for hidden fields that contain payment values that can be modified by the user.
    Affected if Any form uses dynamically-sourced (variable or hidden) payment fields to determine purchase amounts
  3. Confirm payment processing is enabled
    Check if the forms with dynamic payment fields are connected to a payment gateway (such as Stripe, PayPal, or other payment processor) and are actively processing transactions.
    Affected if Forms with dynamic payment fields are configured to process actual payments to users

You are affected if SureForms is installed with a version earlier than 2.11.1 AND you have forms using dynamically-sourced payment fields that process real transactions.

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 SureForms to version 2.11.1 or later. Additionally, implement server-side validation that verifies payment amounts against trusted backend price data rather than trusting client-submitted values for all form submissions.

Recommended fix Moderate confidence

SureForms version 2.11.1 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 below 2.11.1
  5. If vulnerable, click 'Update Now' on the SureForms plugin card to update to version 2.11.1 or later
  6. Alternatively, download the latest version from wordpress.org/plugins/sureforms/ and upload via Plugins > Add New > Upload Plugin
  7. After updating, verify the plugin version shows 2.11.1 or newer in the plugins list
  8. For forms using dynamic payment amounts, test the payment flow to confirm the amount is now properly validated

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

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

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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