dbcve.org
Funnelkit AutomationsWordPress extension · Funnelkit

CVE-2025-1562

CRITICAL · 9.8 CVSS v3.1 Published 2025-06-18
Fix available
A fix is available. Upgrade to 3.6.0 or later.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click Patch available

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 Recover WooCommerce Cart Abandonment, Newsletter, Email Marketing, Marketing Automation By FunnelKit plugin for WordPress is vulnerable to unauthorized arbitrary plugin installation due to a missing capability check on the install_or_activate_addon_plugins() function and a weak nonce hash in all versions up to, and including, 3.5.3. This makes it possible for unauthenticated attackers to install arbitrary plugins on the site that can be leveraged to further infect a vulnerable site.

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 WordPress plugin has a missing capability check on the install_or_activate_addon_plugins() function combined with a weak nonce hash, allowing unauthenticated attackers to install arbitrary plugins on vulnerable sites.

MitigationUpdate to version 3.5.4 or later. If immediate update is not possible, consider disabling the plugin or deploying WAF rules to block unauthorized plugin installation requests, and audit the site for any previously installed malicious plugins.

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.0

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
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/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. Verify Funnelkit Automations plugin is installed
    Log in to WordPress admin, go to Plugins > Installed Plugins, and look for 'Funnelkit Automations' or 'Funnelkit Funnelkit Automations' in the list
    Affected if The plugin appears in the installed plugins list
  2. Check installed plugin version
    In the Plugins page, click the plugin name or view details to see the installed version number. Alternatively, check the plugin's main PHP file header in wp-content/plugins/
    Affected if Version shown is below 3.6.0 (vulnerable versions are < 3.6.0)
  3. Confirm plugin is active
    On the Plugins page, verify the plugin has an 'Active' status under the plugin name
    Affected if Plugin is active and version is below 3.6.0 - the vulnerability is exploitable without authentication when the plugin is enabled
  4. Review recent plugin installation activity
    Check WordPress activity logs or server access logs for requests to wp-admin/admin-ajax.php?action=install_or_activate_addon_plugins or similar plugin installation endpoints
    Affected if Unusual plugin installation requests are found in logs from unauthenticated sources

If the Funnelkit Automations plugin is installed and active with a version lower than 3.6.0, the site is affected by this unauthenticated arbitrary plugin installation 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
Upgrade available Upgrade to 3.6.0 or later
Fixed in 3.6.0
Vendor patch plugins.trac.wordpress.org →
Interim mitigation

Update to version 3.5.4 or later. If immediate update is not possible, consider disabling the plugin or deploying WAF rules to block unauthorized plugin installation requests, and audit the site for any previously installed malicious plugins.

Recommended fix High confidence

Funnelkit Automations version 3.6.0

  1. Update the Funnelkit Automations plugin to version 3.6.0 or later immediately to patch the missing authorization vulnerability
  2. Verify the plugin update was successfully applied by checking the installed version in WordPress admin
  3. Review the site for any unauthorized plugins that may have been installed exploiting this vulnerability
  4. Consider implementing additional security measures such as WordPress firewall plugins to protect against similar vulnerabilities

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

Fix this in Funnelkit Automations Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
7.0 hours of engineering $1,240
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,984.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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