dbcve.org
ClickwhaleWordPress extension · Flowdee

CVE-2025-47612

HIGH · 8.8 CVSS v3.1 Published 2025-05-07
Fix available
A fix is available. Upgrade to 2.4.7 or later.
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
Missing Authorization vulnerability in ClickWhale ClickWhale clickwhale allows Exploiting Incorrectly Configured Access Control Security Levels.This issue affects ClickWhale: from n/a through <= 2.4.6.

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

ClickWhale WordPress plugin versions <= 2.4.6 contain a missing authorization vulnerability (broken access control) that allows attackers to exploit incorrectly configured access control security levels. This likely permits unauthorized users to access administrative functions or perform actions without proper capability checks.

MitigationImplement proper authorization checks (current_user_can() capability verification and nonce validation) on all admin actions and AJAX endpoints. Update to the latest patched version when available.

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

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. Identify ClickWhale plugin installation
    In WordPress admin, go to Plugins > Installed Plugins. Look for 'ClickWhale' or 'Flowdee Clickwhale' in the list of installed plugins.
    Affected if The ClickWhale plugin appears in the installed plugins list
  2. Check if ClickWhale plugin is active
    In the Plugins list, verify whether the ClickWhale plugin has an 'Active' status (not 'Inactive' or 'Must-Use').
    Affected if The plugin shows as Active
  3. Determine installed ClickWhale version
    In the Plugins list, click on the plugin name or view details. Note the version number displayed (typically shown as 'Version x.x.x' under the plugin name).
    Affected if The version number is 2.4.6 or lower, or if the version displayed is less than 2.4.7
  4. Verify WordPress user role configuration
    Navigate to Users > All Users in WordPress admin. Review which user accounts exist and their assigned roles, noting any low-privilege users (e.g., Subscriber, Contributor) who should not have admin access.
    Affected if There are user accounts with roles below Administrator that exist in the system
  5. Check for unauthorized admin access indicators
    Review WordPress activity logs, audit logs, or security plugins for any actions performed by non-Administrator users that modified plugin settings, created redirects, or accessed ClickWhale-specific admin functions.
    Affected if Non-Administrator users have performed actions typically restricted to admin roles, or settings were modified by unexpected users

You are affected if the ClickWhale plugin is installed, active, and running version 2.4.6 or lower (anything below 2.4.7).

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

Implement proper authorization checks (current_user_can() capability verification and nonce validation) on all admin actions and AJAX endpoints. Update to the latest patched version when available.

Recommended fix High confidence

ClickWhale version 2.4.7

  1. Backup your WordPress site and database before updating
  2. Update ClickWhale plugin to version 2.4.7 via WordPress admin dashboard or via wp-cli: wp plugin update clickwhale
  3. Verify the update was successful by checking the plugin version
  4. Test that all ClickWhale functionality works as expected after the update
  5. If using a staging environment, test the update there first before deploying to production

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

Fix this in Clickwhale 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-2025-47612 — 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-47612 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