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

CVE-2025-26899

MEDIUM · 6.5 CVSS v3.1 Published 2025-03-15
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
74/100
Remediation priority · Elevated
Remotely reachable No privileges 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
Cross-Site Request Forgery (CSRF) vulnerability in Recapture Cart Recovery and Email Marketing Recapture for WooCommerce recapture-for-woocommerce allows Cross Site Request Forgery.This issue affects Recapture for WooCommerce: from n/a through <= 1.0.43.

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 Recapture for WooCommerce plugin allows attackers to trick authenticated users into performing unintended actions by forcing their browser to send malicious requests. The plugin lacks proper anti-CSRF token validation on state-changing operations.

MitigationUpdate the Recapture for WooCommerce plugin to the latest version which implements nonce-based CSRF protection for all forms and AJAX endpoints. Until patched, avoid clicking untrusted links while logged into WordPress admin.

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

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/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. Check if Recapture for WooCommerce is installed
    In WordPress admin, go to Plugins > Installed Plugins and search for 'Recapture for WooCommerce' in the list
    Affected if The plugin is not found in the installed plugins list
  2. Identify the installed plugin version
    In the plugins list, locate Recapture for WooCommerce and note the version number displayed beneath the plugin name
    Affected if The version is older than the latest patched version available from the developer
  3. Confirm the plugin is active
    In the plugins list, verify that Recapture for WooCommerce shows as 'Active' (not deactivated)
    Affected if The plugin is active and handling requests
  4. Inspect plugin code for CSRF token validation
    Access plugin files via FTP or file manager, examine form handlers and AJAX endpoint code, and search for nonce validation functions such as wp_verify_nonce(), check_ajax_referer(), or wp_create_nonce()
    Affected if No nonce or CSRF token validation is found in state-changing operations

You are affected if the Recapture for WooCommerce plugin is installed, active, and lacks proper nonce-based CSRF protection in its forms and AJAX endpoints.

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

Update the Recapture for WooCommerce plugin to the latest version which implements nonce-based CSRF protection for all forms and AJAX endpoints. Until patched, avoid clicking untrusted links while logged into WordPress admin.

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

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-26899 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

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