dbcve.org
Funnelkit AutomationsWordPress extension · Funnelkit

CVE-2024-47328

HIGH · 7.2 CVSS v3.1 Published 2024-10-21
Fix available
A fix is available. Upgrade to 3.2.0 or later.
See remediation →
78/100
Remediation priority · High
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
Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection') vulnerability in Aman FunnelKit Automations wp-marketing-automations allows SQL Injection.This issue affects FunnelKit Automations: from n/a through <= 3.1.2.

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 · moderate confidence

SQL Injection vulnerability in the FunnelKit Automations WordPress plugin allows attackers to inject malicious SQL queries through unsanitized input in database operations. The vulnerability exists in versions through 3.1.2 and could allow authenticated attackers to read, modify, or delete database content.

MitigationUpgrade to the latest version of FunnelKit Automations when a patch is available. If immediate patching is not possible, implement WAF rules to block SQL injection attack patterns and restrict database permissions to least privilege.

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

CVSS:3.1/AV:N/AC:L/PR:H/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. Locate the FunnelKit Automations plugin version
    In WordPress admin, go to Plugins > Installed Plugins > FunnelKit Automations and read the version number from the plugin description. Alternatively, inspect the plugin main file (typically /wp-content/plugins/automations-for-woocommerce/automations-for-woocommerce.php or similar) and look for the 'Version:' header in the file comments.
    Affected if The displayed version number is lower than 3.2.0 (for example, 3.1.2, 3.1.1, 3.0.x, etc.)
  2. Confirm the plugin is active
    In WordPress admin, go to Plugins > Installed Plugins and verify that FunnelKit Automations shows as 'Active' under the plugin status.
    Affected if The plugin is installed and currently active with a vulnerable version below 3.2.0
  3. Review WordPress debug logs for SQL errors
    Check the wp-content/debug.log file (if debug logging is enabled in wp-config.php) for any entries containing SQL syntax errors, warnings, or suspicious database queries originating from the FunnelKit Automations plugin files.
    Affected if Log entries show malformed SQL queries with signatures typical of SQL injection attempts against the plugin's database operations
  4. Inspect database user privileges
    Review the WordPress database user privileges in the hosting control panel or via MySQL command: SHOW GRANTS FOR CURRENT_USER;. The database user should have only the minimum privileges required for WordPress operation.
    Affected if The database user has elevated privileges (such as GRANT, DROP, or FILE) beyond what WordPress requires, which could allow a successful SQL injection to modify or delete data

Your environment is affected if FunnelKit Automations plugin version is below 3.2.0 and the plugin is active, regardless of user role, since any authenticated user could potentially exploit the unsanitized SQL input 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.2.0 or later
Fixed in 3.2.0
Interim mitigation

Upgrade to the latest version of FunnelKit Automations when a patch is available. If immediate patching is not possible, implement WAF rules to block SQL injection attack patterns and restrict database permissions to least privilege.

Recommended fix High confidence

FunnelKit Automations version 3.2.0

  1. Log in to the WordPress admin dashboard
  2. Navigate to Plugins > Installed Plugins
  3. Locate FunnelKit Automations (also labeled as wp-marketing-automations)
  4. Check if the current version is below 3.2.0
  5. Click 'Update Now' if an update is available, or manually upload version 3.2.0 or later
  6. After updating, verify the plugin version shows 3.2.0 or higher
  7. Test critical automation workflows to ensure functionality is intact

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
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,930
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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