Multiple Plugins By FunnelKit <= (Various Versions) - Authenticated (Contributor+) Sensitive Information Exposure to Privilege Escalation via Woofunnel Library
Strategic Overview
- Status
- Patched in 3.11.1
- Affected Plugin
- FunnelKit – Funnel Builder for WooCommerce Checkout
- Affected Version
<= 3.11.0.2- CVSS
- 8.8High
- Weakness type
- CWE-200 · Exposure of Sensitive Information to an Unauthorized Actor
- CVE
CVE-2025-7654
At a glance
CVE-2025-7654 is a high-severity Exposure of Sensitive Information to an Unauthorized Actor vulnerability in the FunnelKit WordPress plugin, affecting versions <= 3.11.0.2. It carries a CVSS score of 8.8 (reachable over the network; low attack complexity; high confidentiality, integrity, availability impact). Exploitation requires an authenticated account at Contributor level or above. The issue is fixed in version 3.11.1; sites on affected versions should update now. Disclosed August 2025, reported by wesley (wcraft).
Vulnerability Overview
Multiple FunnelKit plugins are vulnerable to Sensitive Information Exposure via the wf_get_cookie shortcode. This makes it possible for authenticated attackers, with Contributor-level access and above, to extract sensitive data including authentication cookies of other site users, which may make privilege escalation possible. Please note both FunnelKit – Funnel Builder for WooCommerce Checkout AND FunnelKit Automations – Email Marketing Automation and CRM for WordPress & WooCommerce are affected by this.
Technical Analysis
The vector marks this flaw as remotely reachable over the network, with low attack complexity — no special timing or configuration is needed, and no interaction from a victim user. A successful exploit has high impact on confidentiality, integrity, availability — full site compromise territory.
CWE-200: Exposure of Sensitive Information to an Unauthorized Actor
Reaching this weakness in FunnelKit <= 3.11.0.2 takes an account at Contributor level or above. Sensitive information exposure means data the application intended to keep internal is returned to a caller who should not be able to see it.
The disclosed data — credentials, tokens, customer records or internal paths — is usually worth more as material for a follow-up attack than as an end in itself. For FunnelKit the fix is 3.11.1: builds <= 3.11.0.2 are affected, anything from 3.11.1 onward is not.
Remediation
Update to version 3.11.1, or a newer patched version
How does WordSec protect against this?
The fix is the thing that ends this: FunnelKit 3.11.1 closes this, and updating the plugin is the step that ends it.
- Alerts
External References
Related records
Other vulnerabilities in FunnelKit – Funnel Builder for WooCommerce Checkout
- 9.8CVE-2025-26979: Funnel Builder by FunnelKit <= 3.9.0 LFI
CVE-2025-26979 - 8.1CVE-2025-54750: Funnel Builder by FunnelKit <= 3.11.1 LFI
CVE-2025-54750 - 7.5CVE-2026-42381: FunnelKit SQL Injection
CVE-2026-42381 - 7.5CVE-2025-14169: FunnelKit SQL Injection
CVE-2025-14169 - 7.2CVE-2026-57816: FunnelKit Stored XSS
CVE-2026-57816 - 7.2CVE-2026-48966: FunnelKit Stored XSS
CVE-2026-48966 - 6.6CVE-2023-50856: Funnel Builder for WordPress… SQL Injection
CVE-2023-50856 - 6.5CVE-2026-12979: FunnelKit <= 3.15.0.5 Arbitrary File Deletion
CVE-2026-12979
Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C