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

CVE-2025-39564

MEDIUM · 6.5 CVSS v3.1 Published 2025-04-16
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
72/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 WP Trio Conditional Shipping for WooCommerce conditional-shipping-for-woocommerce allows Cross Site Request Forgery.This issue affects Conditional Shipping for WooCommerce: from n/a through <= 3.4.0.

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 Conditional Shipping for WooCommerce WordPress plugin allows attackers to trick authenticated administrators into performing unintended shipping configuration changes. The plugin lacks proper anti-CSRF token validation on state-changing operations.

MitigationImplement anti-CSRF tokens (nonces) on all form submissions and AJAX endpoints, validate nonce presence and origin headers server-side, and add SameSite attribute to authentication cookies.

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
None
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:N/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. Confirm plugin is installed
    Navigate to WordPress admin > Plugins and verify 'Conditional Shipping for WooCommerce' is installed and active
    Affected if Plugin is installed and active, making the CSRF vulnerability potentially exploitable
  2. Identify plugin version
    In WordPress admin > Plugins, click on the plugin name to view details, or inspect the main plugin file header for the 'Version' field
    Affected if Installed version lacks CSRF protection (compare against changelogs or security advisories for the fix version)
  3. Verify WooCommerce is active
    Navigate to WordPress admin > Plugins and confirm WooCommerce is also active
    Affected if WooCommerce is active and the Conditional Shipping plugin handles shipping configuration, creating the attack surface
  4. Inspect plugin code for nonce validation
    Access plugin files via FTP or file manager, open the main PHP file and any admin action files, search for 'wp_nonce_field', 'verify_nonce', or 'check_admin_referer' function calls
    Affected if State-changing operations (form submissions, AJAX endpoints) do not include nonce verification code
  5. Check for SameSite cookie attributes
    In plugin code, search for 'setcookie' or 'session' related functions and verify SameSite=Lax or SameSite=Strict attributes are set on authentication cookies
    Affected if SameSite attribute is missing from cookies, allowing cross-site request forgery to succeed

User is affected if the Conditional Shipping for WooCommerce plugin is active, the installed version predates the CSRF fix, and state-changing admin operations lack nonce validation in the plugin code.

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 anti-CSRF tokens (nonces) on all form submissions and AJAX endpoints, validate nonce presence and origin headers server-side, and add SameSite attribute to authentication cookies.

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
16.0 hours of engineering $2,800
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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