CVE-2026-39671
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 · uneditedCross-Site Request Forgery (CSRF) vulnerability in Dotstore Extra Fees Plugin for WooCommerce woo-conditional-product-fees-for-checkout allows Cross Site Request Forgery.This issue affects Extra Fees Plugin for WooCommerce: from n/a through <= 4.3.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 · high confidenceCross-Site Request Forgery (CSRF) vulnerability in Dotstore Extra Fees Plugin for WooCommerce (woo-conditional-product-fees-for-checkout) allows attackers to induce authenticated users to perform unintended state-changing actions by tricking their browsers into sending malicious requests. The vulnerability affects all versions through 4.3.3 of 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
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:L/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 checksWork through these to decide whether this CVE applies to you.
-
Identify if Dotstore Extra Fees Plugin for WooCommerce is installedAccess WordPress admin dashboard and navigate to Plugins > Installed Plugins. Look for 'Dotstore Extra Fees Plugin for WooCommerce' or similar naming in the plugin list.Affected if The plugin appears in the installed plugins list with that name or similar
-
Verify plugin is active on the WooCommerce siteIn the Plugins list, check if the Dotstore Extra Fees Plugin shows as 'Active' rather than 'Inactive' or 'Must Use'.Affected if Plugin is active and in use on the site
-
Inspect admin forms for CSRF token presenceNavigate to the plugin's admin settings pages (typically under WooCommerce > Extra Fees or similar). View page source (right-click > View Page Source) and search for 'wpnonce', '_wpnonce', or 'nonce' fields in all forms that modify fee configurations, add/remove conditional fees, or alter pricing rules.Affected if Forms modifying fee settings lack _wpnonce or wpnonce hidden input fields
-
Check AJAX endpoints for nonce validationUse browser developer tools > Network tab. Trigger plugin AJAX actions (adding fees, modifying rules, saving settings). Examine the request headers and parameters for presence of a nonce value (typically named 'nonce', 'security', or ending in '_nonce').Affected if AJAX requests that modify plugin settings do not include a valid nonce parameter
-
Test for Referer/Origin header validationUsing a tool like Burp Suite or curl, manually send a state-changing request (such as adding a fee rule) with an incorrect or missing Origin/Referer header to see if the request is still processed.Affected if Requests with mismatched or missing Origin/Referer headers are processed successfully without validation
If the Dotstore Extra Fees Plugin for WooCommerce is active and its admin forms/AJAX endpoints lack proper nonce verification for state-changing operations, the environment is vulnerable to CVE-2026-39671.
Generated from the published advisory. Verify against your own configuration.
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 dataImplement anti-CSRF tokens (nonces) for all state-changing operations in the plugin, verify Origin/Referer headers on POST requests, and apply SameSite cookie attributes to session cookies.
- Consultation3.0 h
- Implementation6.0 h
- Testing3.0 h
- Review / QA2.0 h
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 locallyCheck whether your project pulls in CVE-2026-39671 — 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 sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-39671 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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