dbcve.org
ClickwhaleWordPress extension · Flowdee

CVE-2025-26963

HIGH · 8.8 CVSS v3.1 Published 2025-02-25
Fix available
A fix is available. Upgrade to 2.4.4 or later.
See remediation →
95/100
Remediation priority · Urgent
Remotely reachable No privileges

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
Cross-Site Request Forgery (CSRF) vulnerability in ClickWhale ClickWhale clickwhale allows Cross Site Request Forgery.This issue affects ClickWhale: from n/a through <= 2.4.3.

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

Cross-Site Request Forgery (CSRF) vulnerability in the ClickWhale WordPress plugin (versions up to 2.4.3) allows attackers to perform unauthorized actions on behalf of authenticated administrators. The plugin lacks proper anti-CSRF token validation on state-changing operations, enabling attackers to trick authenticated users into executing unintended requests.

MitigationImplement WordPress nonces (wp_create_nonce, wp_verify_nonce) on all form submissions and AJAX actions within the plugin to validate request origin and intent.

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

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
Required
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/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 ClickWhale plugin version
    In WordPress admin, go to Plugins > Installed Plugins. Find 'ClickWhale' (or 'Flowdee Clickwhale') and read the version number displayed beneath the plugin name. Alternatively, inspect the plugin main file header via file browser or FTP at /wp-content/plugins/clickwhale/clickwhale.php and look for the 'Version:' field.
    Affected if The installed version is 2.4.3 or lower (any version below 2.4.4).
  2. Verify the plugin is active
    In WordPress admin, go to Plugins > Installed Plugins. Confirm that ClickWhale shows as 'Active' rather than 'Inactive'.
    Affected if The plugin is active and the version is below 2.4.4.
  3. Inspect admin forms for missing CSRF tokens
    Access the ClickWhale plugin settings pages in the WordPress admin (usually under Settings > ClickWhale or a dedicated ClickWhale menu item). Open browser developer tools (F12), switch to the Network tab, and submit a settings form. Inspect the POST request payload - check if a nonce, token, or security parameter is included alongside the form data.
    Affected if State-changing forms (settings save, link creation, etc.) submit without any anti-CSRF token or nonce parameter.
  4. Check for SameSite cookie attribute on admin sessions
    Log into WordPress admin, open browser developer tools, go to Application > Cookies > admin URL. Examine the wordpress_ session cookie. Check if the SameSite attribute is set to 'Strict' or 'Lax', or if it is missing/empty.
    Affected if The admin session cookie lacks SameSite attribute or is set to 'None' without Secure flag.

You are affected if the ClickWhale plugin version is below 2.4.4 and the plugin is active with state-changing admin forms lacking anti-CSRF token validation.

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

Implement WordPress nonces (wp_create_nonce, wp_verify_nonce) on all form submissions and AJAX actions within the plugin to validate request origin and intent.

Recommended fix Moderate confidence

2.4.4

  1. Backup your WordPress site before performing any updates
  2. Navigate to Dashboard > Plugins in WordPress admin
  3. Locate the Clickwhale plugin in the installed plugins list
  4. Click 'Update now' on the Clickwhale plugin if an update is available, or manually upload version 2.4.4
  5. Verify the plugin updated successfully by checking the installed plugins page

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
  • Testing2.0 h
  • Review / QA1.0 h
9.0 hours of engineering $1,600
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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