CVE-2026-62073

Stripe Payment Forms by WP Full Pay – Accept Credit Card Payments, Donations & Subscriptions <= 8.5.6 - Missing Authorization

2026-10-01 11:56
Ananda Dhakal

Strategic Overview

Status
Patched in 8.5.7
Affected Plugin
Stripe Payment Forms by WP Full Pay – Accept Credit Card Payments, Donations & Subscriptions
Affected Version
<= 8.5.6
CVSS
5.3Medium
Weakness type
CWE-862 · Missing Authorization
CVE
CVE-2026-62073
View all Stripe Payment Forms by WP Full Pay – Accept Credit Card Payments, Donations & Subscriptions vulnerabilities

At a glance

CVE-2026-62073 is a medium-severity Missing Authorization vulnerability in the Stripe Payment Forms by WP Full Pay WordPress plugin, affecting versions <= 8.5.6. 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.7; sites on affected versions should update now. Disclosed October 2026, reported by Ananda Dhakal.

Vulnerability Overview

The Stripe Payment Forms by WP Full Pay – Accept Credit Card Payments, Donations & Subscriptions plugin for WordPress is vulnerable to unauthorized access in all versions up to, and including, 8.5.6. This is due to a missing capability check on a function. 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-862: Missing Authorization

Reaching this weakness in Stripe Payment Forms by WP Full Pay <= 8.5.6 takes a caller who can reach the endpoint. A missing authorization check means a function is reachable by anyone who can reach the endpoint, because the code never asks whether the caller is allowed to perform the action.

Any user who can reach the endpoint gets to run an action reserved for higher-privileged roles, from reading protected data to changing settings or content. For Stripe Payment Forms by WP Full Pay the fix is 8.5.7: builds <= 8.5.6 are affected, anything from 8.5.7 onward is not.

Remediation

Update to version 8.5.7, or a newer patched version

How does WordSec protect against this?

Because it turns on account access, WordSec's login security is the relevant layer: role-based two-factor, captcha and brute-force limits raise the cost of getting the account this needs. None of that substitutes for the fix: Stripe Payment Forms by WP Full Pay 8.5.7 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-62073https://www.wordfence.com/threat-intel/vulnerabilities/id/ed5ce18d-184e-44ce-9201-d63763014c84https://nvd.nist.gov/vuln/detail/CVE-2026-62073

Related records

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