dbcve.org
Cross-Site Request Forgery (CSRF)Weakness · CWE-352

CVE-2025-24647

MEDIUM · 5.4 CVSS v3.1 Published 2025-01-24
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
61/100
Remediation priority · Elevated
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 datafeedr WooCommerce Cloak Affiliate Links woocommerce-cloak-affiliate-links allows Cross Site Request Forgery.This issue affects WooCommerce Cloak Affiliate Links: from n/a through <= 1.0.35.

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

Cross-Site Request Forgery (CSRF) vulnerability in the datafeedr WooCommerce Cloak Affiliate Links plugin (versions up to 1.0.35) allows attackers to trick authenticated administrators into performing unintended actions, such as modifying affiliate link settings, by leveraging the lack of anti-CSRF token validation on plugin admin actions.

MitigationImplement WordPress nonces (anti-CSRF tokens) on all form submissions and AJAX actions within the plugin, and validate these nonces on the server side before processing any state-changing requests.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

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
None
Integrity
Low
Availability
Low

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:L/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 plugin directory
    Check for the 'datafeedr-woocommerce-cloak-affiliate-links' folder in wp-content/plugins/ on the WordPress file system
    Affected if The plugin folder exists on the server
  2. Identify the installed version
    Open the main plugin PHP file (typically datafeedr-woocommerce-cloak-affiliate-links.php) and locate the Version header in the plugin comment block or a version constant
    Affected if The version number is 1.0.35 or lower (including any subversion)
  3. Confirm the plugin is active
    Query the WordPress 'active_plugins' option in the wp_options table, or check via WordPress admin plugins list
    Affected if The plugin appears in the list of active plugins
  4. Inspect admin action handlers for nonce validation
    Review the plugin PHP code for admin action handlers (actions using 'admin_init', 'admin_post_', or AJAX hooks). Search for 'wp_verify_nonce', 'check_admin_referer', or 'check_ajax_referer' calls within these handlers
    Affected if The plugin handles admin state-changing requests (such as saving affiliate link settings) without verifying a nonce token

A user is affected if the datafeedr WooCommerce Cloak Affiliate Links plugin is installed, active, and version 1.0.35 or lower, with admin actions lacking nonce verification.

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.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Implement WordPress nonces (anti-CSRF tokens) on all form submissions and AJAX actions within the plugin, and validate these nonces on the server side before processing any state-changing requests.

Have this fixed 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 help mitigating

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-24647 — 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-24647 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