Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessFingerprint WordPress site for vulnerable plugin
-
DeliveryIdentify or guess portal session identifier
-
ExploitSend unauthenticated request to portal data endpoint
-
ExecutionBypass missing confirmation-step check
-
ImpactRetrieve victim customer billing and subscription records
Vulnerability Assessment
| Weakness |
CWE
OWASP Top 10:2025
A01:2025 - Broken Access Control
ASVS 5.0
V14 - Data Protection Data exposure prevention
MITRE ATT&CK
2 techniques across 2 tactics: Collection, Discovery The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up. |
| Exploitation Conditions | No authentication is required - the CVSS vector PR:N confirms unauthenticated exploitation. The target WordPress site must have the Stripe Payment Forms by WP Full Pay plugin installed and activated in a version prior to 8.5.1, and the customer portal feature must be in use (i.e., at least one customer has initiated a portal session). Exploitation is limited to reading other customers' subscription and billing data (confidentiality only); no write or availability impact is possible. The attacker must be able to reach the WordPress site over the network, but no special network position is required. The attack is limited to sites that actually process Stripe subscriptions through this specific plugin. |
| Impact | The CVSS 3.1 vector AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N scores 5.3 Medium and accurately reflects the attack surface: fully network-reachable, zero prerequisites, but limited to confidentiality impact only. EPSS at 0.18% (7th percentile) is low, which is notable given a public POC already exists - this divergence suggests the exploit has not yet been widely used in automated campaigns, possibly because the plugin has a narrower deployment footprint than mass-targeted software. The vulnerability is not listed in CISA KEV, so active exploitation is not confirmed. The real-world risk is disproportionate to the CVSS score for any site processing real customer payment data: exposure of subscription and billing records constitutes financial PII with GDPR and PCI-DSS compliance implications. Even a small e-commerce operator running this plugin faces regulatory exposure if customer billing records are read by unauthorized parties. The risk priority should be elevated above the raw score for any site with active paying customers. |
| Exploit ScenarioDerived | An attacker enumerates WordPress sites running the vulnerable plugin (detectable via standard WordPress plugin fingerprinting) and sends a crafted unauthenticated request to the customer portal data-return endpoint, supplying a session identifier that has not completed the confirmation flow. The server responds with subscription details and billing records for the associated customer account. A public exploit is available per WPScan intelligence, lowering the skill bar for this attack. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Aug 26, 2026
Stripe Payment Forms by WP Full Pay plugin for WordPress (all versions before 8.5.1) exposes customer subscription and billing data to unauthenticated network attackers due to a missing session-confirmation check in the customer portal workflow. The plugin returns sensitive financial records before verifying that a portal session has completed its confirmation step, enabling any unauthenticated user to read billing information belonging to a different customer. A publicly available exploit exists per WPScan intelligence, though EPSS sits at 0.18% (7th percentile), indicating limited observed exploitation despite the low-barrier attack path.
RemediationAI
Update the Stripe Payment Forms by WP Full Pay plugin to version 8.5.1 or later; this is confirmed as the vendor-released patch per the WPScan advisory (https://wpscan.com/vulnerability/2d4fc012-9f80-43cc-b68d-96842700fe2f/). If immediate patching is not possible, a compensating control is to temporarily disable the customer portal feature within the plugin's settings, preventing exposure of the vulnerable endpoint entirely - this will interrupt self-service subscription management for customers but eliminates the attack surface. Restricting access to the WordPress site's plugin endpoints via WAF rules targeting the portal callback path is a partial mitigation but requires knowing the exact endpoint path, which may be guessable. Plugin auto-update should be enabled in WordPress to prevent recurrence.
Affected VersionsENISA
Affected Packages
Source: OSV (Open Source Vulnerabilities)
Affects your stack
Affects 1 package in euvd
Checking this CVE against your own stacks and servers is part of the Basic plan and up.
Technical ContextAI · show details
The root cause is CWE-200 (Exposure of Sensitive Information to an Unauthorized Actor), arising in the plugin's Stripe customer portal integration. The plugin is designed to allow existing customers to manage subscriptions via a portal session; the vulnerable code path returns subscription and billing records tied to a session identifier without first confirming the session has reached its final confirmation state. This is a business-logic authorization flaw rather than a memory-safety or injection issue. The affected product is identified by CPE cpe:2.3:a:unknown:stripe_payment_forms_by_wp_full_pay:*:*:*:*:*:*:*:* and runs as a WordPress plugin wrapping the Stripe Billing API.
Know when Stripe Payment Forms By Wp Full Pay gets its next vulnerability
- Watch products and get an email when something new is published
- Check this CVE against your own stack and servers
- Exploit and PoC references, threat intelligence from 22 sources
No credit card · 7-day full trial
Severity by source
AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N
Network-reachable with no auth or interaction needed; impact confined to partial confidentiality loss of customer billing records, no integrity or availability impact.
Primary rating from Vendor (WPScan).
CVSS VectorVendor: WPScan
Lifecycle Timeline
4DescriptionCVE.org
The Stripe Payment Forms by WP Full Pay WordPress plugin before 8.5.1 does not properly verify that a customer portal session has completed its confirmation step before returning data, allowing unauthenticated users to read another customer's subscription and billing information.
Threat Intelligence Overview
How this decision was reached
The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.
What every action level means
SSVC AssessmentENISA
Priority Score
Attack Technique
Information disclosure occurs when an application unintentionally exposes sensitive data that aids attackers in reconnaissance or directly compromises security.
Payment amount manipulation in Stripe Payment Forms by WP Full Pay (WordPress plugin) before version 8.5.2 allows any un
Insecure Direct Object Reference (IDOR) in the Stripe Payment Forms by WP Full Pay WordPress plugin before 8.5.1 allows
Stripe Payment Forms by WP Full Pay WordPress plugin before version 8.5.5 exposes an Insecure Direct Object Reference (I
EUVD-2026-66288
GHSA-7q4v-225q-qmcp
NVD
CVE.org
EPSS
Vulnrichment
Exploit-DB