CVE-2026-74991: WPForms access control bypass in Stripe payment handling

CVE-2026-74991 · Severity: medium · CVSS 6.8 · Published 2026-09-24

WPForms is a WordPress form builder plugin that integrates with Stripe for payment processing. The plugin fails to verify that Stripe payment objects belong to the current form before processing them, allowing an unauthenticated attacker to initiate refunds and cancel subscriptions on payments created by other applications connected to the site owner's Stripe account. This could result in unauthorized financial transactions and service interruptions for legitimate customers.

Technologies: WPForms. Vendors: WPForms.

Quick answers

Is CVE-2026-74991 exploited in the wild?
No. Junglewise Threat Intelligence has no report of CVE-2026-74991 being exploited in the wild.
How severe is CVE-2026-74991?
Medium severity, with a CVSS score of 6.8, published 24 September 2026.
Which products and versions are affected?
WPForms 1.8.8.2 to 2.0.1.1.
Is there a fix for CVE-2026-74991?
A patch was published on 2026-09-24: Fixed in version 2.0.2 Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
How is CVE-2026-74991 attacked?
It is attacked over the network, in a software library.
Am I affected by CVE-2026-74991?
Check whether you run WPForms at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

Technical details

The vulnerability is a broken access control issue (CWE-284) in the Stripe payment intent handling logic. When processing public form submissions, the plugin accepts Stripe payment objects without validating ownership, allowing unauthenticated users to trigger refunds and subscription cancellations against arbitrary payments on the Stripe account. The vulnerability affects versions before 2.0.2 and is exploitable via network without authentication or user interaction.

Affected products

  • WPForms WPForms 1.8.8.2 to 2.0.1.1

Timeline

  • 2026-09-22: disclosed
  • 2026-09-24: patched: Fixed in version 2.0.2

References

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.