dbcve.org
Funnelkit AutomationsWordPress extension · Funnelkit

CVE-2025-12468

MEDIUM · 5.3 CVSS v3.1 Published 2025-11-05
Fix available
A fix is available. Upgrade to 3.6.4.2 or later.
See remediation →
62/100
Remediation priority · Elevated
Remotely reachable No privileges 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
The FunnelKit Automations – Email Marketing Automation and CRM for WordPress & WooCommerce plugin for WordPress is vulnerable to Sensitive Information Exposure in all versions up to, and including, 3.6.4.1 via the '/wc-coupons/' REST API endpoint. This is due to the endpoint being marked as a public API (`public_api = true`), which results in the endpoint being registered with `permission_callback => '__return_true'`, bypassing all authentication and capability checks. This makes it possible for unauthenticated attackers to extract sensitive data including all WooCommerce coupon codes, coupon IDs, and expiration status.

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 Automations plugin for WordPress exposes a REST API endpoint at '/wc-coupons/' that is incorrectly configured with public_api = true, causing it to register with permission_callback => '__return_true'. This bypasses all authentication and capability checks, allowing unauthenticated attackers to retrieve all WooCommerce coupon codes, coupon IDs, and expiration status.

MitigationUpdate the FunnelKit Automations plugin to version 3.6.5 or later which removes the public API flag from the coupon endpoint and implements proper authentication. Alternatively, disable the plugin until an update can be applied.

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

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Funnelkit AutomationsWordPress extension
Affected:< 3.6.4.2

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
None
User interaction
None
Scope
Unchanged
Confidentiality
Low
Integrity
None
Availability
None

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

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. Verify FunnelKit Automations plugin is installed
    In WordPress admin, go to Plugins > Installed Plugins and look for 'Funnelkit Automations' or check the plugins directory for /wp-content/plugins/funnelkit-automations/
    Affected if The plugin is present on the WordPress site
  2. Check the installed plugin version
    In WordPress admin Plugins page, click on the plugin to view details, or inspect the main plugin file header in /wp-content/plugins/funnelkit-automations/ for the Version: field
    Affected if Version is less than 3.6.4.2 (vulnerable versions)
  3. Test the vulnerable REST API endpoint
    Send a GET request to /wp-json/funnelkit-automations/v1/wc-coupons/ or /wc-coupons/ without providing any authentication tokens or credentials
    Affected if The endpoint returns HTTP 200 with coupon data (code, id, expiry) without requiring authentication
  4. Verify if the endpoint is publicly accessible
    Inspect the plugin source code in /includes/rest/ directory for the wc-coupons endpoint registration; look for 'public_api' => true or 'permission_callback' => '__return_true'
    Affected if The endpoint is registered with public_api enabled or permission_callback set to '__return_true' allowing unauthenticated access

A site is affected if the FunnelKit Automations plugin version is below 3.6.4.2 AND the /wc-coupons/ REST endpoint returns coupon data without requiring authentication.

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
Upgrade available Upgrade to 3.6.4.2 or later
Fixed in 3.6.4.2
Interim mitigation

Update the FunnelKit Automations plugin to version 3.6.5 or later which removes the public API flag from the coupon endpoint and implements proper authentication. Alternatively, disable the plugin until an update can be applied.

Recommended fix High confidence

FunnelKit Automations version 3.6.4.2 or later

  1. Log in to the WordPress admin dashboard
  2. Navigate to Plugins > Installed Plugins
  3. Find 'FunnelKit Automations' (or 'FunnelKit Automations – Email Marketing Automation and CRM for WordPress & WooCommerce')
  4. Check the current version number to confirm it is below 3.6.4.2
  5. If an update is available, click 'Update Now' to upgrade to the latest version
  6. Alternatively, navigate to Dashboard > Updates and select the FunnelKit Automations plugin to update
  7. After updating, verify the new version is 3.6.4.2 or higher
  8. Test that the /wc-coupons/ REST API endpoint now requires authentication (should return 401/403 for unauthenticated requests)

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

Fix this in Funnelkit Automations Scoped from the published advisory
  • Consultation1.0 h
  • Implementation1.0 h
  • Testing2.0 h
  • Review / QA1.0 h
5.0 hours of engineering $860
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-12468 — 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-12468 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