VulnerabilityPublished 7 Nov 2026

CVE-2026-109991: FunnelKit Payment Gateway for Stripe WooCommerce (WordPress plugin) · Insecure Direct Object Reference

Affects FunnelKit Payment Gateway for Stripe WooCommerce (WordPress plugin)Source CVE Database V5

Compare

Not known to be exploited · CVSS 7.5 High.

Data as of 7 Nov 2026, 11:50 UTC

CVSS 3.1 base score

7.5High

How severe the flaw is on the 0–10 CVSS scale.

Thin evidence

One scorer or none

CVSS scores by source
CNA (Wordfence)	CVSS 3.1	7.5

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N

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

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Network: The vulnerable component is bound to the network stack and the set of possible attackers extends beyond the other options listed, up to and including the entire Internet. Such a vulnerability is often termed 'remotely exploitable' and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers).
Attack Complexity: Low: Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success against the vulnerable component.
Privileges Required: None: The attacker is unauthorized prior to attack, and therefore does not require any access to settings or files to carry out an attack.
User Interaction: None: The vulnerable system can be exploited without any interaction from any user.
Scope: Unchanged: An exploited vulnerability can only affect resources managed by the same security authority. In this case, the vulnerable component and the impacted component are either the same, or both are managed by the same security authority.
Confidentiality: High: There is total loss of confidentiality, resulting in all resources within the impacted component being divulged to the attacker. Alternatively, access to only some restricted information is obtained, but the disclosed information presents a direct, serious impact.
Integrity: None: There is no loss of integrity within the impacted component.
Availability: None: There is no impact to availability within the impacted component.

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 7 Nov 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 7 Nov 2026.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponized: A Metasploit exploit module or Exploit-DB entry exists (Metasploit scanner modules do not count), or CISA SSVC or the CVSS exploit maturity reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Affected software

Product	Affected	Fixed in
teamfunnelkitFunnelKit Payment Gateway for Stripe WooCommerce	Affected <=1.15.0.2	Fixed in–

AI-suggested

Until a fix is available, restrict access to the order-pay pages and monitor for suspicious activity. Avoid exposing sensitive data in client-side scripts. Follow vendor updates closely for an official patch.

Description

The FunnelKit Payment Gateway for Stripe WooCommerce plugin for WordPress contains an authorization bypass vulnerability (CWE-639) in all versions up to 1.15.0.2. This flaw allows unauthenticated attackers to access full billing personally identifiable information (PII) of any store order by manipulating the 'order-pay' query parameter. The vulnerability arises from missing validation on a user-controlled key, enabling attackers to enumerate sequential order IDs and retrieve sensitive customer data embedded in JavaScript objects on the page. Exploitation is possible even when WooCommerce itself rejects the order-pay request, due to independent script localization calls in the plugin.

Impact

An attacker can obtain full billing PII of any order in the affected WooCommerce store without authentication by enumerating order IDs. This leads to a significant privacy breach, exposing customer names, email addresses, phone numbers, and full street addresses. The vulnerability does not affect integrity or availability but has a high confidentiality impact. There is no evidence of active exploitation in the wild as of the published date.

Summary

CVE-2026-109991 is an authorization bypass vulnerability in the FunnelKit Payment Gateway for Stripe WooCommerce plugin for WordPress, affecting versions up to and including 1.15.0.2. The vulnerability is caused by insecure direct object reference (IDOR) via the 'order-pay' WP query variable, which lacks proper validation. This allows unauthenticated attackers to enumerate order IDs and access full billing PII such as name, email, phone number, and street address. The sensitive data is exposed through the inline JavaScript object 'fkwcs_data' localized by wp_localize_script on the order-pay page. Notably, this exposure occurs even if WooCommerce rejects the order-pay request, as the plugin's script localization bypasses WooCommerce's order-key validation.

CWE-639Authorization Bypass Through User-Controlled Key (opens in a new tab)
Base weaknessLikelihood of exploit: HighCWE Top 25 (2025): #24OWASP Top 10 A01:2025: Broken Access Control (opens in a new tab)
The system's authorization functionality does not prevent one user from gaining access to another user's data or record by modifying the key value identifying the data.
Architecture and Design
For each and every data access, ensure that the user has sufficient privilege to access the record that is being requested.
Architecture and Design · Implementation
Make sure that the key that is used in the lookup of a specific user's record is not controllable externally by the user or that any tampering can be detected.
Architecture and Design
Use encryption in order to make it more difficult to guess other legitimate values of the key or associate a digital signature with the key so that the server can verify that there has been no tampering.
OWASP Cheat Sheets
Access Control (opens in a new tab)
Authorization Testing Automation (opens in a new tab)
Cross-Site Request Forgery Prevention (opens in a new tab)
Insecure Direct Object Reference Prevention (opens in a new tab)
Authorization (opens in a new tab)
OWASP ASVS 4.0.3
V4.1.2 (opens in a new tab)
V4.2.1 (opens in a new tab)
V8.3.8 (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 7 Nov 2026, 11:50 UTC

WeaknessesCWE-639

Technical details

References

Community reviews

Related threats