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

CVE-2026-25024

MEDIUM · 5.4 CVSS v3.1 Published 2026-02-03
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 Blair Williams ThirstyAffiliates thirstyaffiliates allows Cross Site Request Forgery.This issue affects ThirstyAffiliates: from n/a through <= 3.11.9.

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 ThirstyAffiliates WordPress plugin (versions up to 3.11.9) allows authenticated administrators to be tricked into performing unintended actions such as modifying affiliate links or settings via maliciously crafted requests.

MitigationUpdate ThirstyAffiliates to the latest patched version; alternatively, implement WordPress nonces (anti-CSRF tokens) on all form submissions and AJAX requests within the plugin.

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. Confirm ThirstyAffiliates is installed
    Log into WordPress admin panel, navigate to Plugins > Installed Plugins, and look for ThirstyAffiliates in the list. Alternatively, check the /wp-content/plugins/ directory for a thirsty-affiliates folder via FTP or file manager.
    Affected if ThirstyAffiliates plugin folder exists in the WordPress installation
  2. Identify installed plugin version
    In WordPress admin, go to Plugins > Installed Plugins, find ThirstyAffiliates, and note the version number displayed below the plugin name. Or, open the main plugin file (usually thirsty-affiliates.php) and look for the 'Version:' header comment.
    Affected if Version displayed is 3.11.9 or lower
  3. Compare version against affected range
    Take the identified version number and compare it to the affected range. The vulnerability affects versions up to and including 3.11.9.
    Affected if Installed version is 3.11.9 or any earlier version (e.g., 3.11.8, 3.11.0, 3.10.5, etc.)
  4. Verify admin access is enabled
    Confirm that administrator-level users exist and have access to the WordPress admin dashboard where ThirstyAffiliates settings and affiliate link management are accessible.
    Affected if Administrator accounts exist and can access the ThirstyAffiliates settings panel

You are affected if the ThirstyAffiliates plugin is installed and the installed version is 3.11.9 or lower.

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
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Update ThirstyAffiliates to the latest patched version; alternatively, implement WordPress nonces (anti-CSRF tokens) on all form submissions and AJAX requests within the plugin.

Recommended fix Moderate confidence

Latest version of ThirstyAffiliates (version > 3.11.9)

  1. 1. Log in to the WordPress admin dashboard
  2. 2. Navigate to Plugins > Installed Plugins
  3. 3. Locate ThirstyAffiliates plugin
  4. 4. Check current installed version (should be <= 3.11.9)
  5. 5. If an update is available, click 'Update Now' to install the latest version
  6. 6. Verify the update completed successfully
  7. 7. Test plugin functionality to ensure no regressions

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

Have this fixed Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,490
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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