dbcve.org
Missing AuthorizationWeakness · CWE-862

CVE-2026-2890

HIGH · 7.5 CVSS v3.1 Published 2026-03-13
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 Formidable Forms plugin for WordPress is vulnerable to a payment integrity bypass in all versions up to, and including, 6.28. This is due to the Stripe Link return handler (`handle_one_time_stripe_link_return_url`) marking payment records as complete based solely on the Stripe PaymentIntent status without comparing the intent's charged amount against the expected payment amount, and the `verify_intent()` function validating only client secret ownership without binding intents to specific forms or actions. This makes it possible for unauthenticated attackers to reuse a PaymentIntent from a completed low-value payment to mark a high-value payment as complete, effectively bypassing payment for goods or services.

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 Formidable Forms plugin's Stripe Link return handler marks payments as complete based only on the Stripe PaymentIntent status without validating that the charged amount matches the expected amount. Additionally, the verify_intent() function only checks client secret ownership without binding PaymentIntents to specific forms or actions. This allows unauthenticated attackers to reuse a low-value PaymentIntent to complete a high-value payment, effectively stealing goods or services.

MitigationImplement server-side amount verification by comparing the PaymentIntent's charged amount against the expected amount before marking payment complete, and bind PaymentIntents to specific forms/actions during creation to prevent reuse across different payments.

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 Formidable Forms plugin is installed
    Check your WordPress plugins directory or admin panel for the Formidable Forms plugin and note its current version number
    Affected if Formidable Forms plugin is installed and running
  2. Identify the installed Formidable Forms version
    Locate the main plugin file (usually formidable.php or class-formidable.php) and read the version constant or header
    Affected if The installed version does not include the fix for amount validation in Stripe payments
  3. Verify Stripe Link integration is active
    Check Formidable Forms settings for Stripe/Stripe Link payment method configuration; look for connected Stripe account and enabled payment forms
    Affected if Stripe Link payment method is enabled and configured for any form
  4. Inspect the payment completion handler
    Examine the Stripe return handler code that processes successful payments - look for verify_intent() function calls and check if amount validation occurs against expected values before marking payment complete
    Affected if The payment handler marks payments complete based solely on PaymentIntent status without comparing the charged amount to the expected/form-defined amount
  5. Check for PaymentIntent binding to forms
    Review how PaymentIntents are created and verified - verify that PaymentIntents are bound to specific form IDs or action IDs during creation and that verify_intent() validates this binding
    Affected if PaymentIntents can be reused across different forms or payment amounts without binding validation

A user is affected if they have Formidable Forms with Stripe Link enabled and the payment handler does not validate that the charged amount matches the expected amount or bind PaymentIntents to specific forms before completion.

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 amount verification by comparing the PaymentIntent's charged amount against the expected amount before marking payment complete, and bind PaymentIntents to specific forms/actions during creation to prevent reuse across different payments.

Recommended fix High confidence

Formidable Forms version 6.29 or later

  1. 1. Navigate to the WordPress admin dashboard
  2. 2. Go to Plugins > Installed Plugins
  3. 3. Locate Formidable Forms plugin
  4. 4. If an update is available, click 'Update Now' to upgrade to version 6.29 or later
  5. 5. Alternatively, download the latest version from wordpress.org/plugins/formidable-forms/ and upload via Plugins > Add New > Upload Plugin
  6. 6. After updating, verify the Stripe payment integration works correctly by testing a payment

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-2890 — 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-2890 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