FunnelKit Checkout Bug Exposes Billing Details
If your WooCommerce store runs the FunnelKit – Funnel Builder for WooCommerce Checkout plugin at version 3.16.0.6 or older, update it to the latest version today, because a flaw (CVE-2026-107746) can let anyone on the internet read customers' billing details without logging in.
This post is for owners of WooCommerce stores, agencies that build them, and anyone who installed FunnelKit to make a nicer checkout or thank-you page. You will learn what the flaw is, how to tell whether you are exposed, the exact steps to fix it, and what to do afterward. No security background needed.
What the FunnelKit vulnerability is, in plain English
FunnelKit is a WordPress plugin that builds checkout flows and thank-you pages for WooCommerce stores. A thank-you page is the page a customer sees after paying. It often shows their order details.
According to the NVD entry for CVE-2026-107746, the plugin does not properly check whether the person asking for order data is allowed to see it. Security people call this a missing authorization check (the weakness type is CWE-862, listed in the record). Think of a hotel desk that hands over any guest's room details to anyone who asks for a room number.
The record says an attacker who is not logged in can pull billing personal information for any order on the site. That information includes:
- Full name
- Street address
- Email address
- Phone number
The attacker does this by submitting an order ID. Order IDs are sequential numbers (1001, 1002, 1003 and so on), so they are easy to guess one after another. Security folks call that enumerable.
Is your store actually affected?
There are two conditions in the record, and both must be true:
- You run the FunnelKit – Funnel Builder plugin at version 3.16.0.6 or lower.
- You have a FunnelKit thank-you page that shows the
[wfty_order_meta]or[wfty_order_total]shortcode.
A shortcode is a small tag in square brackets that WordPress swaps for real content when the page loads. These two tags print order details onto the thank-you page.
The record says the flaw is only exploitable on sites where such a page exists. So a site with the plugin but without those shortcodes on a thank-you page is described as not exploitable through this route. You should still update. Old plugin versions are a bad habit to keep.
Quick decision table
| Your situation | Exposed per the record? | What to do |
|---|---|---|
| Version 3.16.0.6 or older, thank-you page uses one of the shortcodes | Yes | Update now, then run the checks below |
| Version 3.16.0.6 or older, no thank-you page with those shortcodes | Not through this route | Update anyway |
| Newer than 3.16.0.6, updated from the WordPress plugin directory | Outside the listed range | Confirm the version and keep auto-updates on |
| Plugin not installed | No | Nothing to do for this issue |
Which version fixes it?
The NVD record lists the vulnerable range as all versions up to and including 3.16.0.6. It does not name a fixed version. One reference in the record is a download link for version 3.17.0 of the plugin, but the record does not say outright that this is the fix.
So the safe advice is this: update to the newest version available in your WordPress dashboard, then read the plugin's changelog on its WordPress.org page to confirm the authorization issue is covered. Do not install a plugin ZIP from a random site. Use the Plugins screen in WordPress or the official WordPress.org plugin directory.
Step-by-step: what to do right now
1. Take a backup
Make a fresh backup of your files and database with your host's tool or your backup plugin. Updates rarely break things, but a backup makes any mistake cheap to undo.
2. Check your version
In WordPress, go to Plugins > Installed Plugins and find FunnelKit – Funnel Builder for WooCommerce Checkout. The version number sits under the name. If you have command line access with WP-CLI (a tool for managing WordPress from a terminal), run:
wp plugin get funnel-builder --field=version
3. Update the plugin
Click Update now on the Plugins screen. Or, with WP-CLI:
wp plugin update funnel-builder
Then run the version check again. If you see an update message for a paid FunnelKit add-on as well, update that too and read its changelog.
4. Find where your thank-you pages use the shortcodes
In your WordPress dashboard, open the FunnelKit (Funnel Builder) menu and open each thank-you page in its editor. They may not appear under Pages. Look for the [wfty_order_meta] or [wfty_order_total] shortcode. Page builders can store content in unusual places, so a search box may miss some. If you use WP-CLI and your database prefix is the default wp_, these two queries list where either shortcode is stored. The first checks the main post content. The second checks post metadata, where page builders such as Elementor often keep their content:
wp db query "SELECT ID, post_title, post_type, post_status FROM wp_posts WHERE post_content LIKE '%wfty_order_meta%' OR post_content LIKE '%wfty_order_total%';"
wp db query "SELECT post_id, meta_key FROM wp_postmeta WHERE meta_value LIKE '%wfty_order_meta%' OR meta_value LIKE '%wfty_order_total%';"
Change wp_ if your prefix is different. These queries only read data. They do not change anything. An empty result from either query is not proof that you are clear, because content can be stored in other places. Open each thank-you page in the FunnelKit editor and check it by eye too.
5. If you cannot update today, use a stopgap
This is a temporary measure and not a fix. Since the record ties the exposure to those two shortcodes, removing them from the thank-you page, or setting that page to draft, may cut off the described route until you can update. Removing the shortcodes is based on the record's description. It is not a confirmed mitigation from the vendor. Setting the thank-you page to draft may change what customers see after paying, so test a checkout afterward. Write down what you changed so you can restore it later.
6. Turn on automatic updates for security fixes
In Plugins > Installed Plugins, click Enable auto-updates next to FunnelKit. For a small store, getting a security fix quickly usually matters more than the small chance an update causes a hiccup. Check your store after updates now and then.
How to check whether someone already pulled customer data
The record does not say this flaw is being used in real attacks, and we are not claiming it is. Still, it is reasonable to look for signs of misuse, because the method is simple and the data is valuable to scammers.
Here is what you can do without being an expert:
- Ask your host for access logs covering the weeks before you updated. Look for repeated requests from one IP address that cycle through many different order IDs or order numbers, on the thank-you page or on related checkout or admin-ajax or REST URLs.
- Watch for odd customer reports. Customers who say they got phishing emails or texts that mention a recent order from your shop are worth taking seriously.
- Look at your security plugin's activity log, if you have one, for bursts of requests to checkout or thank-you URLs.
If you find signs of misuse, follow our guide for a hacked or compromised website. Depending on where you and your customers live, you may also have legal duties to notify people after a data leak. A lawyer or your payment provider can tell you what applies to you.
How to protect WooCommerce customer information beyond this one bug
This flaw is a good reminder that customer data leaks do not always come from a break-in. Sometimes a plugin just hands the data to whoever asks. A few habits lower that risk in general:
- Keep fewer plugins. Every plugin is code you must trust and keep updated. Delete the ones you do not use.
- Update on a schedule. Check for plugin updates weekly, and sooner when you hear about a security fix.
- Show less on public pages. A thank-you page rarely needs a full address and phone number. If a page can be reached from a link, treat it as public.
- Use accounts with the least access needed. Staff who answer emails do not need administrator rights.
- Add a second layer. Strong admin passwords and two-factor login protect your dashboard. They would not have stopped this flaw, which needs no login, but they matter for other attacks.
- Check your outside basics. Our free security headers tool and email spoofing checker look at settings anyone can see from the outside.
The OWASP Top 10 lists broken access control as a leading web risk. That is the family this bug belongs to, and it is a common one in plugins.
Why a scanner may not catch this
A missing authorization check is hard for automated tools to spot. The page loads, nothing crashes, and the data looks normal. A person has to ask the question: should this visitor be allowed to see this order? That is one reason we explain how manual and automated testing differ. A plugin vulnerability scanner can tell you that you run a vulnerable version, and that is useful. It cannot tell you whether your own custom pages or settings leak data in other ways.
Where to read the primary sources
- The NVD record for CVE-2026-107746 lists the severity as High, with a CVSS score of 7.5. CVSS is a standard 0 to 10 scoring system for how serious a flaw is. The record was published on 2026-10-16, and its NVD status is Deferred. That is a processing status, so recheck the page for updates.
- The Wordfence entry for this vulnerability is linked from the record.
- The plugin's changelog on its WordPress.org page is the best place to confirm which release addresses the issue.
The CVSS vector in the record says the attack works over the network, is low in complexity, needs no account and no user interaction, and affects confidentiality (the data) but not integrity or availability. In everyday words: it is easy to try, and it exposes information. It does not let the attacker change your store or take it offline.
Key takeaways
- Update FunnelKit – Funnel Builder for WooCommerce Checkout now. Versions up to and including 3.16.0.6 are listed as vulnerable in CVE-2026-107746.
- The record says exposure requires a thank-you page that shows
[wfty_order_meta]or[wfty_order_total]. Find those pages and review them. - No fixed version is named in the record. Update to the latest release and read the changelog to confirm.
- Check your logs and customer reports for signs of misuse, and get legal advice if customer data may have been exposed.
- Keep fewer plugins, turn on auto-updates for security fixes, and treat any page reachable by link as public.
What to do next
Updating fixes this one plugin. It does not tell you what else on your store might leak data. If you want a person to look at the whole site, a Bug Circuit audit is a manual security test of one website, ending in a written report with every issue, its severity, evidence and fix steps. It is not a compliance certificate or a multi-week enterprise pentest. See plans and prices (Essential is $49 one-time), or start with the free website security check. If you are unsure how worried to be, our guide on whether your website is hackable is a calm place to begin.
A real human security engineer audits your whole site by hand and sends a full report: every issue, its severity, and the exact fix. From $49, with a 14-day money-back guarantee.
See pricing