Skip to main content

WP Full Stripe Free CVE-2026-42378

| EUVDEUVD-2026-36810 MEDIUM
Authentication Bypass Using an Alternate Path or Channel (CWE-288)
2026-06-15 Patchstack GHSA-hmqv-f2v5-fjff
6.5
CVSS 3.1 · Vendor: Patchstack
View

Attack ChainAIDerived

Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain

  1. Access
    Register or obtain subscriber WordPress account
  2. Delivery
    Authenticate to target WordPress site
  3. Exploit
    Identify vulnerable plugin endpoint via source review or enumeration
  4. Execution
    Send crafted authenticated request to bypass authorization check
  5. Impact
    Retrieve sensitive Stripe or payment data

Vulnerability Assessment

Weakness
CWE
OWASP Top 10:2025
A07:2025 - Authentication Failures
ASVS 5.0
V6 - Authentication Alternate path authentication
Exploitation Conditions

Exploitation requires the attacker to hold a valid subscriber-level (or higher) WordPress user account on the target site - this is the sole prerequisite. On WordPress sites with open user registration enabled (the default on many installations), any internet user can self-register to obtain this access level. On closed-registration sites, the attacker must already possess credentials for any valid account. The plugin WP Full Stripe Free version 8.4.1 or earlier must be installed and active. No specific plugin feature or non-default configuration mode is identified in the available data as a prerequisite - the vulnerability appears to exist in the plugin's standard authentication handling. Exploitation is limited to information disclosure (C:H, I:N, A:N); there is no indication of write or destructive capability. No physical access, specific platform variant, or additional privilege is required beyond the subscriber account.

Impact

The NVD CVSS 3.1 score is 6.5 (Medium), with vector AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N. The PR:L metric is the critical limiting factor - exploitation requires a subscriber-level WordPress account, which on sites with open user registration represents a very low barrier; on private or closed-registration sites, the attacker must first obtain or possess credentials. Attack complexity is low (AC:L) with no user interaction, meaning once credentials are available, exploitation is straightforward. The Confidentiality impact is rated High (C:H), consistent with potential exposure of Stripe payment data, customer records, or subscription information - data with direct regulatory and financial implications. No EPSS score was provided in the input data, so probabilistic exploitation likelihood cannot be assessed quantitatively. The vulnerability is not listed in CISA KEV, and no public POC has been identified, both of which reduce immediate urgency. However, WordPress plugin vulnerabilities of this class are historically popular targets due to the large install base and the low sophistication required once a subscriber account is obtained. Sites with open user registration should treat this as higher priority than the raw score implies.

Exploit ScenarioDerived

An attacker targeting a WordPress e-commerce site running WP Full Stripe Free registers a free subscriber account (or uses a previously obtained low-privilege credential) and then directly invokes a plugin REST API endpoint or AJAX action that lacks proper capability verification, retrieving Stripe customer records, subscription identifiers, or payment metadata for other site users. No public POC has been identified, but the low complexity (AC:L) and well-understood WordPress plugin authentication bypass pattern make independent reproduction feasible for a moderately skilled attacker.

This Month Plan within 30 days. Why: MEDIUM severity (CVSS 4.0-6.9).
No patch listed yet 0.4% exploitation probability (EPSS)

Get an e-mail when this CVE is exploited, patched or re-scored. Free account.

Alert me

AnalysisAIv1 – Jun 15, 2026

Broken authentication in WP Full Stripe Free (WordPress plugin by Themeisle) versions 8.4.1 and earlier permits subscriber-level authenticated users to bypass authorization controls and access restricted functionality, resulting in high-confidence information disclosure. The vulnerability (CWE-288) targets the Stripe payment integration plugin's internal access control logic, allowing a low-privileged WordPress user to reach endpoints or data intended only for higher-privileged roles. No public exploit code has been identified at time of analysis, and the vulnerability is not listed in the CISA Known Exploited Vulnerabilities catalog.

RemediationAI

No confirmed patched version was identified in the available intelligence data; the Patchstack advisory at https://patchstack.com/database/wordpress/plugin/wp-full-stripe-free/vulnerability/wordpress-wp-full-stripe-free-plugin-8-4-1-broken-authentication-vulnerability should be consulted for the current patch status and exact fix version as the vendor may have released an update subsequent to this analysis. As an immediate compensating control, administrators should disable the WP Full Stripe Free plugin on publicly accessible sites until a patched release is confirmed - this fully eliminates the attack surface at the cost of disabling Stripe payment functionality. If disabling is not operationally feasible, restrict WordPress user registration to prevent unauthenticated visitors from obtaining the subscriber credentials needed to exploit this flaw (Settings > General > uncheck 'Anyone can register'); note this does not protect against attacks by existing subscriber accounts. Additionally, audit existing subscriber-role accounts for any unauthorized or suspicious registrations. Monitor Patchstack and the WordPress plugin repository for an updated release.

Affected VersionsENISA

WP Full Stripe Free n/a ≤8.4.1

Affected Packages

euvd wp_full_stripe_free no fix

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

WP Full Stripe Free (CPE: cpe:2.3:a:themeisle:wp_full_stripe_free:*:*:*:*:*:*:*:*) is a WordPress plugin by Themeisle that integrates Stripe payment processing into WordPress sites. CWE-288 (Authentication Bypass Using an Alternate Path or Channel) describes a class of flaws where an application implements a primary authentication gate but leaves an alternative code path - typically a REST API endpoint, AJAX action handler, or internal function - accessible without proper capability checks. In WordPress plugin architecture, this often manifests when plugin-registered endpoints validate nonces but omit role or capability verification, allowing any authenticated WordPress user (including subscribers, the lowest default role) to invoke privileged operations. Given the 'Information Disclosure' tag and C:H/I:N/A:N CVSS impact profile, the likely scenario is that sensitive Stripe-related data (e.g., subscription details, payment records, customer identifiers) is exposed through such an inadequately guarded endpoint.

Know when Wp Full Stripe Free 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

Vendor (Patchstack) PRIMARY 6.5 MEDIUM
AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N
vuln.today AI 6.5 MEDIUM

Network-accessible WordPress endpoint requires only a subscriber account (PR:L); purely read-only data exposure yields C:H with no integrity or availability impact.

3.1 AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N
4.0 AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N

Primary rating from Vendor (Patchstack).

CVSS VectorVendor: Patchstack

Attack Vector
Network
Attack Complexity
Low
Privileges Required
Low
User Interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

DescriptionCVE.org

Subscriber Broken Authentication in WP Full Stripe Free <= 8.4.1 versions.

Threat Intelligence Overview

EPSS Score
0.4%
Top 69% exploitable
Data Quality
5 sources
Confidence: Medium

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.

SignalValue
Severity MEDIUM
CISA KEV No
Public POC No
EPSS 0.4%
Patch available No
Active threat No
Deciding rule
MEDIUM severity (CVSS 4.0-6.9)
What every action level means
Emergency Immediate action required. Criteria: CRITICAL + in CISA KEV (actively exploited) without patch, OR CRITICAL + EPSS > 30% without patch, OR CRITICAL + active threat signals without patch.
Act Now Prioritize within 24-48h. Criteria: in KEV with patch available, OR CRITICAL + public POC, OR HIGH + EPSS > 10%, OR CRITICAL + active threat, OR any CRITICAL severity.
This Week Schedule remediation this week. Criteria: HIGH severity (CVSS 7.0-8.9). Patch within normal change window.
This Month Plan within 30 days. Criteria: MEDIUM severity (CVSS 4.0-6.9), lower exploitation probability. Include in regular patch cycle.
Monitor Track and reassess. Criteria: LOW severity (CVSS 0.1-3.9), minimal exploitation risk. No immediate action needed.

SSVC AssessmentENISA

SSVC Decision· derived
Scheduled
Exploitation
None
System Exposure· derived
Open
Automatable
No
Human Impact· derived
Medium
Technical Impact
Partial

Priority Score

32
Low Medium High Critical
KEV: 0
EPSS: 0
CVSS: +32
PoC: 0
Weaponized: 0
Threat intel: 0
Gov advisory: 0

Attack Technique

Information disclosure occurs when an application unintentionally exposes sensitive data that aids attackers in reconnaissance or directly compromises security.

This site uses cookies essential for authentication and security. No tracking or analytics cookies are used. Privacy Policy