dbcve.org
ClickwhaleWordPress extension · Flowdee

CVE-2024-51715

HIGH · 8.5 CVSS v3.1 Published 2025-01-07
Fix available
A fix is available. Upgrade to 2.4.2 or later.
See remediation →
91/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
Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection') vulnerability in ClickWhale ClickWhale clickwhale allows Blind SQL Injection.This issue affects ClickWhale: from n/a through <= 2.4.1.

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

A blind SQL injection vulnerability exists in the ClickWhale WordPress plugin (versions <= 2.4.1). The flaw allows unauthenticated attackers to inject malicious SQL queries through insufficiently sanitized user inputs, potentially enabling data exfiltration or database manipulation. The 'blind' classification indicates the application does not return SQL error messages directly, requiring attackers to infer results through behavioral differences.

MitigationUpgrade ClickWhale to the latest version (2.4.2 or later) which contains the patched code. If no patch is available, temporarily disable the plugin until a fix is released. Additionally, implement Web Application Firewall (WAF) rules to detect and block SQL injection attempts as a defense-in-depth measure.

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
ClickwhaleWordPress extension
Affected:< 2.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
Low
User interaction
None
Scope
Changed
Confidentiality
High
Integrity
None
Availability
Low

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

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 ClickWhale plugin installation
    In WordPress admin, go to Plugins > Installed Plugins and find 'ClickWhale' or use WP-CLI: wp plugin list --name=clickwhale
    Affected if The plugin is not found in the installation
  2. Identify the installed ClickWhale version
    In WordPress admin, click on the plugin to view details and read the version number, or check the plugin header in /wp-content/plugins/clickwhale/clickwhale.php for 'Version:'
    Affected if Version is 2.4.1 or lower, or the version cannot be determined (older or unlisted version)
  3. Confirm the plugin is active
    In WordPress admin > Plugins, verify that ClickWhale shows as 'Active', or run: wp plugin status clickwhale
    Affected if The plugin is active and serving pages (unauthenticated SQL injection requires the plugin to be active)
  4. Check WordPress version as context
    Review WordPress core version at Dashboard > Updates or via WP-CLI: wp core version
    Affected if Not directly relevant to this CVE (plugin vulnerability), but useful for full vulnerability context

Your environment is affected if ClickWhale version 2.4.1 or lower is installed and the plugin is active on your WordPress site.

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 2.4.2 or later
Fixed in 2.4.2
Interim mitigation

Upgrade ClickWhale to the latest version (2.4.2 or later) which contains the patched code. If no patch is available, temporarily disable the plugin until a fix is released. Additionally, implement Web Application Firewall (WAF) rules to detect and block SQL injection attempts as a defense-in-depth measure.

Recommended fix High confidence

2.4.2

  1. Backup your WordPress site database and files before proceeding
  2. Update ClickWhale plugin to version 2.4.2 or later through the WordPress admin dashboard (Plugins > ClickWhale > Update Now)
  3. Alternatively, download version 2.4.2 from the official WordPress plugin repository and upload manually
  4. Verify the plugin version shows 2.4.2 or higher after update
  5. Test that the link management functionality works correctly

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

Fix this in Clickwhale Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA3.0 h
19.0 hours of engineering $3,380
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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