Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessEnumerate sequential WooCommerce order IDs
-
ExploitSubmit IDs to thank-you-page shortcode endpoint
-
ImpactHarvest billing PII for all orders
Vulnerability Assessment
| Weakness |
CWE
OWASP Top 10:2025
A01:2025 - Broken Access Control
ASVS 5.0
V8 - Authorization Authorization checks on every request
MITRE ATT&CK
1 technique across 1 tactic: Privilege Escalation The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up. |
| Exploitation Conditions | Exploitable only on sites where a FunnelKit thank-you page exists that renders the [wfty_order_meta] or [wfty_order_total] shortcode; this specific page/shortcode configuration is the hard prerequisite. Given that precondition, no authentication, privileges, or user interaction are required (CVSS PR:N/UI:N) and order IDs are sequential/enumerable, enabling automated bulk extraction. The limiting factor is the non-default requirement that the vulnerable shortcode be published on a reachable thank-you page - stores not using these shortcodes are not exposed. |
| Impact | This is a genuine medium-to-high priority data-exposure flaw, but not a drop-everything emergency. The Wordfence-provided CVSS vector (AV:N/AC:L/PR:N/UI:N/C:H/I:N/A:N = 7.5) is internally consistent with the description: a remote, unauthenticated attacker can read confidential data with no user interaction and no privileges. The impact is scoped to confidentiality only (I:N/A:N) - attackers harvest billing PII but cannot alter orders or disrupt the site. Crucially, exploitation is gated by a site-specific precondition not reflected in the raw score: a FunnelKit thank-you page rendering the [wfty_order_meta] or [wfty_order_total] shortcode must already exist, so the real-world attack surface is narrower than AC:L/PR:N alone implies. No EPSS score, CISA KEV listing, or public POC was provided in the intelligence set; status is therefore 'no public exploit identified at time of analysis.' The sequential, enumerable order IDs make bulk scraping trivial once a vulnerable page is found, which raises practical severity for affected sites even though it is not confirmed as actively exploited. Net: a real priority for FunnelKit/WooCommerce operators who use thank-you-page shortcodes, lower urgency for those who do not. |
| Exploit ScenarioDerived | An unauthenticated attacker locates a FunnelKit thank-you page that renders the [wfty_order_meta] or [wfty_order_total] shortcode, then scripts requests iterating through sequential order IDs (1, 2, 3, …). Because the plugin never verifies the requester owns the order, each request returns the customer's full name, street address, email, and phone number, allowing wholesale scraping of the store's customer PII. No public exploit code was identified in the provided data, but the attack is low-complexity and requires no authentication. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Oct 16, 2026
An authorization bypass in the FunnelKit Funnel Builder for WooCommerce Checkout WordPress plugin (all versions up to and including 3.16.0.6) lets unauthenticated attackers pull billing PII - full name, street address, email address, and phone number - for any WooCommerce order on a site by simply iterating sequential order IDs. Exploitation requires no authentication, privileges, or user interaction (CVSS:3.1/AV:N/AC:L/PR:N/UI:N, 7.5), and the sequential ID space makes automated bulk extraction practical, so a single vulnerable store can leak its entire customer billing dataset. The hard precondition is that a FunnelKit thank-you page rendering the [wfty_order_meta] or [wfty_order_total] shortcode must exist and be reachable - stores that do not use these shortcodes are not exposed. No public exploit code has been identified at time of analysis and there is no CISA KEV listing; Wordfence-coordinated disclosure tracks it as a genuine medium-to-high priority data-exposure flaw rather than a drop-everything emergency.
RemediationAI
Vendor-released patch: update FunnelKit Funnel Builder to 3.17.0 or later (package: https://downloads.wordpress.org/plugin/funnel-builder.3.17.0.zip), which is the fix version referenced by the advisory at https://www.wordfence.com/threat-intel/vulnerabilities/id/bc9883b7-ea99-41e4-adf6-a3988f616a3f?source=cve; because WordPress auto-updates plugins, verify the installed version in the admin Plugins list after the update completes. If immediate patching is not possible, the most effective compensating control is to remove the [wfty_order_meta] and [wfty_order_total] shortcodes from any publicly reachable FunnelKit thank-you page or unpublish those pages entirely - the trade-off is that customers lose the order-confirmation detail and total displays on those pages, so substitute a generic confirmation message. Deactivating the FunnelKit plugin stops the exposure completely but disables all funnels, upsells, and thank-you pages, which is normally only acceptable as a short-term emergency measure. WAF or reverse-proxy rules that reject unauthenticated requests carrying the wfty order-lookup parameters (or that throttle repeated sequential order_id probes to the Admin-AJAX/REST endpoints) reduce bulk scraping, but they are signature-dependent and can be bypassed by parameter variation, so treat them as interim only. Note that suppressing order IDs is not a realistic mitigation here - WooCommerce order numbering is sequential by design and retroactively randomizing it breaks payment-gateway and fulfillment integrations. After remediating, review web logs for high-volume sequential order_id requests to those endpoints to determine whether customer billing data was already harvested, and factor that exposure into any privacy-breach notification obligations.
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
FunnelKit (formerly WooFunnels) is a commercial WordPress/WooCommerce plugin whose thank-you-pages module renders post-purchase confirmation pages via shortcodes such as [wfty_order_meta] and [wfty_order_total]. The root cause is CWE-862 (Missing Authorization): the code path that resolves an order from a client-supplied identifier in modules/thankyou-pages/includes/class-wfty-data.php (referenced lines 286, 318 and 328) and the page handling in modules/thankyou-pages/class-wffn-thank-you-wc-pages.php (line 429) fails to verify that the requester owns or is otherwise authorized to view the referenced WooCommerce order. Because WooCommerce order IDs are WordPress post IDs that are allocated sequentially, an attacker who can reach the shortcode-rendering endpoint can enumerate order_id values and harvest billing data at scale. There is no nonce/ownership check gating the lookup, which is why the vulnerability is exploitable pre-authentication. The affected package is identified by CPE cpe:2.3:a:teamfunnelkit:funnelkit_-_funnel_builder_plugin_for_woocommerce_checkout (all versions), with the vendor-advisory version ceiling being 3.16.0.6; the plugin is distributed through the WordPress.org repository and via the vendor.
Know when Woocommerce 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:H/I:N/A:N
Remote unauthenticated read of PII across all orders justifies AV:N/PR:N/C:H; no integrity or availability impact (I:N/A:N); scope unchanged as only plugin data is exposed.
Primary rating from Vendor (Wordfence).
CVSS VectorVendor: Wordfence
DescriptionCVE.org
The FunnelKit - Funnel Builder for WooCommerce Checkout plugin for WordPress is vulnerable to authorization bypass in all versions up to, and including, 3.16.0.6 This is due to the plugin not properly verifying that a user is authorized to perform an action. This makes it possible for unauthenticated attackers to retrieve billing PII - including full name, street address, email address, and phone number - for any WooCommerce order on the site by submitting an enumerable sequential order ID. This is only exploitable on sites where a FunnelKit thank-you page exists that renders the [wfty_order_meta] or [wfty_order_total] shortcode.
Executive ViewAI
A high-severity authorization flaw in the FunnelKit Funnel Builder for WooCommerce Checkout WordPress plugin (all versions through 3.16.0.6) allows unauthenticated parties to harvest the billing name, street address, email, and phone number of every customer order on an affected store simply by walking sequential order numbers. Any store that publishes a reachable FunnelKit thank-you page using the [wfty_order_meta] or [wfty_order_total] shortcode can have its entire customer billing dataset extracted at scale, exposing the organization to privacy-regulation penalties, customer notification costs, and reputational harm. No public exploit code or confirmed active exploitation has been identified, and no vendor patch is currently available, so exposure must be managed through interim controls until a fix ships.
No vendor-released patch identified at time of analysis. Interim mitigations: remove or disable the [wfty_order_meta] and [wfty_order_total] shortcodes and unpublish any thank-you page rendering them until a fix is available; require authentication or a valid order key before the page returns order data; apply WAF rate-limiting and virtual patching to block sequential order-ID enumeration; and monitor web logs for bulk order-ID scraping patterns.
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
Authentication bypass attacks exploit flaws in the verification mechanisms that control access to systems and applications.
More in Woocommerce
View allThe WooCommerce plugin through 3.x for WordPress has a Directory Traversal Vulnerability via a /wp-content/plugins/wooco
Unauthenticated arbitrary file upload in Addify's Request a Quote for WooCommerce plugin, affecting all versions up to a
The WooCommerce Help Scout WordPress plugin before 2.9.1 (https://woocommerce.com/products/woocommerce-help-scout/) allo
WooCommerce 7.1.0 contains a remote code execution vulnerability that allows attackers to execute arbitrary PHP code by
Unauthenticated path traversal in OrderConvo (the "Admin and Customer Messages After Order for WooCommerce" plugin), aff
Unauthenticated remote attackers can seize control of the payment configuration on WordPress stores running the Fundiin
Ultimate WooCommerce Gift Cards 3.0.2 is affected by a file upload vulnerability in the Custom GiftCard Template that ca
Unauthenticated attackers can exploit the Walletdoc Payment Gateway for WooCommerce plugin before version 1.8.5 to execu
Unauthenticated SQL injection in the ELEX WooCommerce Request a Quote WordPress plugin (all versions before 2.4.1) allow
Unauthenticated, network-reachable attackers can read the WooCommerce API consumer key and secret stored by the MgoSync
Unauth. Rated high severity (CVSS 7.5), this vulnerability is remotely exploitable, no authentication required, low atta
An issue was discovered in the NAB Transact extension 2.1.0 for the WooCommerce plugin for WordPress. Rated high severit
EUVD-2026-102649
GHSA-fjvp-gr2j-2xrc
NVD
CVE.org
EPSS
Vulnrichment
Exploit-DB