dbcve.org
Information ExposureWeakness · CWE-200

CVE-2025-7654

HIGH · 8.8 CVSS v3.1 Published 2025-08-19
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
94/100
Remediation priority · Urgent
Remotely reachable Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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 summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

The FunnelKit plugins contain a vulnerable shortcode (wf_get_cookie) that improperly exposes sensitive data. Authenticated users with Contributor-level access or higher can use this shortcode to extract authentication cookies from other site users, potentially enabling privilege escalation to higher-privileged accounts.

MitigationImmediately disable or restrict access to the wf_get_cookie shortcode in both FunnelKit – Funnel Builder for WooCommerce Checkout and FunnelKit Automations plugins. Apply any available vendor patches, or remove the shortcode functionality entirely if not required for business operations.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

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

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Check if FunnelKit plugins are installed
    In WordPress admin, go to Plugins > Installed Plugins and look for 'FunnelKit - Funnel Builder for WooCommerce Checkout' or 'FunnelKit Automations'. Alternatively, check the /wp-content/plugins/ directory for folders starting with 'funnelkit'.
    Affected if Either FunnelKit plugin is installed and active
  2. Identify the installed FunnelKit version
    In WordPress admin, go to Plugins > Installed Plugins, click on the FunnelKit plugin, and read the version number from the plugin details. Or inspect the main plugin PHP file for a 'Version:' header comment.
    Affected if Version is unknown or unpatched (no fixed version specified in CVE data)
  3. Verify the wf_get_cookie shortcode exists
    Search the FunnelKit plugin files for the string 'wf_get_cookie' using grep, grep -r 'wf_get_cookie' /wp-content/plugins/funnelkit* or by searching in a code editor. Also check if the shortcode is registered via add_shortcode('wf_get_cookie', ...).
    Affected if The shortcode function is found in the plugin code
  4. Confirm Contributor-level or higher users exist
    In WordPress admin, go to Users and review the user list. Check if any users have the Contributor, Author, Editor, or Administrator role.
    Affected if At least one user with Contributor-level access or higher exists on the site
  5. Check if shortcode execution is possible
    Create a test post or page and attempt to insert the [wf_get_cookie] shortcode. Alternatively, use a WordPress user with Contributor access to attempt shortcode execution in a post draft.
    Affected if The shortcode executes and returns output containing cookie data or sensitive information

If FunnelKit plugins are installed, the wf_get_cookie shortcode is present, and users with Contributor-level access or higher exist, the environment is likely affected by this vulnerability.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Immediately disable or restrict access to the wf_get_cookie shortcode in both FunnelKit – Funnel Builder for WooCommerce Checkout and FunnelKit Automations plugins. Apply any available vendor patches, or remove the shortcode functionality entirely if not required for business operations.

Recommended fix Moderate confidence

Latest patched versions available on WordPress.org plugin repository (check plugin changelogs for security fixes addressing CVE-2025-7654)

  1. Check the WordPress plugin repository for FunnelKit – Funnel Builder for WooCommerce Checkout and FunnelKit Automations – Email Marketing Automation and CRM for the latest patched versions
  2. Navigate to Plugins > Installed Plugins in WordPress admin
  3. Update both FunnelKit plugins to their latest available versions
  4. If an update is not immediately available, consider temporarily disabling the wf_get_cookie shortcode functionality or restricting shortcode usage to administrator-level users only
  5. After updating, verify that the wf_get_cookie shortcode has been removed or properly secured
  6. Audit user accounts with Contributor-level access and above to ensure no unauthorized cookie theft has occurred

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed Scoped from the published advisory
  • Consultation3.0 h
  • Implementation4.0 h
  • Testing2.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,980
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,168.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-7654 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-7654 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data