Stripe Payment Forms by WP Full Pay – Accept Credit Card Payments, Donations & Subscriptions < 8.5.1 - Unauthenticated Information Exposure
Strategic Overview
- Status
- Patched in 8.5.1
- Affected Plugin
- Stripe Payment Forms by WP Full Pay – Accept Credit Card Payments, Donations & Subscriptions
- Affected Version
< 8.5.1- CVSS
- 5.3Medium
- Weakness type
- CWE-200 · Exposure of Sensitive Information to an Unauthorized Actor
- CVE
CVE-2026-77758
At a glance
CVE-2026-77758 is a medium-severity Exposure of Sensitive Information to an Unauthorized Actor vulnerability in the Stripe Payment Forms by WP Full Pay WordPress plugin, affecting versions < 8.5.1. 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.1; sites on affected versions should update now. Disclosed August 2026, reported by Vaibhav Narkhede.
Vulnerability Overview
The Stripe Payment Forms by WP Full Pay – Accept Credit Card Payments, Donations & Subscriptions plugin for WordPress is vulnerable to Sensitive Information Exposure in all versions up to 8.5.1 (exclusive). This makes it possible for unauthenticated attackers to extract customer subscription and billing data.
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-200: Exposure of Sensitive Information to an Unauthorized Actor
Reaching this weakness in Stripe Payment Forms by WP Full Pay < 8.5.1 takes no account at all. Sensitive information exposure means data the application intended to keep internal is returned to a caller who should not be able to see it.
The disclosed data — credentials, tokens, customer records or internal paths — is usually worth more as material for a follow-up attack than as an end in itself. For Stripe Payment Forms by WP Full Pay the fix is 8.5.1: builds < 8.5.1 are affected, anything from 8.5.1 onward is not.
Remediation
Update to version 8.5.1, 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.1 closes this, and updating the plugin is the step that ends it.
- Login Security
- Alerts
External References
Related records
Other vulnerabilities in Stripe Payment Forms by WP Full Pay – Accept Credit Card Payments, Donations & Subscriptions
- 7.5CVE-2025-9322: Stripe Payment Forms <= 8.3.1 SQL Injection
CVE-2025-9322 - 7.2CVE-2026-61960: Stripe Payment Forms by WP Full Pay Stored XSS
CVE-2026-61960 - 5.3CVE-2026-80311: Stripe Payment Forms by WP Full Pay IDOR
CVE-2026-80311 - 5.3CVE-2026-77789: Stripe Payment Forms by WP Full Pay IDOR
CVE-2026-77789 - 5.3CVE-2026-16734: Stripe Payment Forms by WP… Missing Authorization
CVE-2026-16734 - 5.3CVE-2026-12432: Stripe Payment Forms by WP… Unauthenticated Payment
CVE-2026-12432 - 4.9CVE-2025-58789: WP Full Stripe Free <= 8.2.5 SQL Injection
CVE-2025-58789 - 4.4CVE-2023-46088: WP Full Stripe Free <= 7.0.5 Stored XSS
CVE-2023-46088
Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C