CVE-2025-47473
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 pimwick PW WooCommerce Bulk Edit pw-bulk-edit allows Cross Site Request Forgery.This issue affects PW WooCommerce Bulk Edit: from n/a through <= 2.134.
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 confidenceCross-Site Request Forgery (CSRF) vulnerability in the PW WooCommerce Bulk Edit plugin allows attackers to trick authenticated administrators into unknowingly executing bulk operations on WooCommerce products (such as modifying prices, inventory, or product data). The plugin lacks proper anti-CSRF token validation on its bulk edit forms and AJAX endpoints, enabling malicious requests to be processed when a logged-in admin visits a crafted page.
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 checksWork through these to decide whether this CVE applies to you.
-
Verify PW WooCommerce Bulk Edit plugin is installedIn WordPress admin, go to Plugins > Installed Plugins and search for 'PW WooCommerce Bulk Edit'. Check if it appears in the list and is activated.Affected if The plugin is installed and active in WordPress
-
Locate the plugin version numberIn the plugins list, click on the plugin name or view the plugin file header in wp-content/plugins/pw-woocommerce-bulk-edit/ (or similar path) to find the Version: X.X.X entry in the main plugin PHP file.Affected if A version number is returned from the plugin files
-
Inspect bulk edit form files for nonce fieldsExamine the plugin PHP files that render bulk edit forms (typically in the admin/ or includes/ folders). Look for instances of wp_nonce_field, wp_nonce_url, or check_admin_referer in the functions that handle bulk edit form rendering.Affected if The bulk edit form files contain NO nonce-related function calls (wp_nonce_field, check_admin_referer, wp_verify_nonce) near form definitions
-
Check AJAX handlers for nonce validationSearch plugin PHP files for AJAX action handlers (add_action('wp_ajax_...')) and examine whether they verify nonces using wp_verify_nonce or check_admin_referer before processing bulk operations.Affected if AJAX handlers that process bulk edits lack nonce verification calls or the verification is missing before sensitive operations
-
Review the main plugin file for CSRF protectionsOpen the primary plugin PHP file and search for 'nonce' or 'csrf' patterns. Verify if nonces are created, stored, and validated when bulk edit requests are processed.Affected if No nonce validation logic is present in the code that handles bulk edit POST/GET requests
You are affected if the PW WooCommerce Bulk Edit plugin is installed and its code lacks proper nonce token validation on bulk edit forms and AJAX endpoints.
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 WordPress nonce tokens on all bulk edit forms and AJAX actions, verify nonces on the server side before processing any bulk operations, and configure SameSite attributes for session cookies.
- Consultation2.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,664.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-47473 — 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-2025-47473 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