CVE-2026-80311

Stripe Payment Forms by WP Full Pay – Accept Credit Card Payments, Donations & Subscriptions < 8.5.5 - Unauthenticated Insecure Direct Object Reference

2026-08-27 00:00
Farid Narimanov

Strategic Overview

Status
Patched in 8.5.5
Affected Plugin
Stripe Payment Forms by WP Full Pay – Accept Credit Card Payments, Donations & Subscriptions
Affected Version
< 8.5.5
CVSS
5.3Medium
Weakness type
CWE-639 · Authorization Bypass Through User-Controlled Key
CVE
CVE-2026-80311
View all Stripe Payment Forms by WP Full Pay – Accept Credit Card Payments, Donations & Subscriptions vulnerabilities

At a glance

CVE-2026-80311 is a medium-severity Authorization Bypass Through User-Controlled Key vulnerability in the Stripe Payment Forms by WP Full Pay WordPress plugin, affecting versions < 8.5.5. It carries a CVSS score of 5.3 (reachable over the network; low attack complexity). Exploitation requires no authentication. The issue is fixed in version 8.5.5; sites on affected versions should update now. Disclosed August 2026, reported by Farid Narimanov.

Vulnerability Overview

The Stripe Payment Forms by WP Full Pay – Accept Credit Card Payments, Donations & Subscriptions plugin for WordPress is vulnerable to Insecure Direct Object Reference in all versions up to 8.5.5. This is due to missing validation on a user controlled key. This makes it possible for unauthenticated attackers to perform an unauthorized action.

Technical Analysis

The vector marks this flaw as remotely reachable over the network, with low attack complexity — no special timing or configuration is needed, and no privileges on the target site, and no interaction from a victim user.

CWE-639: Authorization Bypass Through User-Controlled Key

Reaching this weakness in Stripe Payment Forms by WP Full Pay < 8.5.5 takes no account at all. Authorization bypass through a user-controlled key, often called insecure direct object reference, means the application looks up a record by an identifier from the request without checking that the caller owns it.

Changing a number in the request is enough to read or modify other users' records, which on commerce and membership sites means customer data. For Stripe Payment Forms by WP Full Pay the fix is 8.5.5: builds < 8.5.5 are affected, anything from 8.5.5 onward is not.

Remediation

Update to version 8.5.5, or a newer patched version

How does WordSec protect against this?

This one needs no account at all, which puts it outside what login hardening can reach; WordSec's login security narrows the account-level paths around it, and the firewall is what inspects the request itself. None of that substitutes for the fix: Stripe Payment Forms by WP Full Pay 8.5.5 closes this, and updating the plugin is the step that ends it.

  • Login Security
  • Alerts

External References

https://www.cve.org/CVERecord?id=CVE-2026-80311https://www.wordfence.com/threat-intel/vulnerabilities/id/41f6c1da-381d-4dd6-a68f-b5511d3e5a1fhttps://nvd.nist.gov/vuln/detail/CVE-2026-80311

Related records

Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C