CVE-2026-3589
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 · uneditedThe WooCommerce WordPress plugin from versions 5.4.0 to 10.5.2 does not properly handle batch requests, which could allow unauthenticated users to make a logged in admin call non store/WC REST endpoints, and create arbitrary admin users via a CSRF attack for example.
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 confidenceThe WooCommerce WordPress plugin (versions 5.4.0-10.5.2) lacks proper validation of batch request origins, enabling CSRF attacks where unauthenticated attackers can trick authenticated administrators into unknowingly triggering requests that create arbitrary admin user accounts on the target WordPress site.
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
- High
- Privileges
- None
- User interaction
- Required
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:H/I:H/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 the installed WooCommerce versionLog into the WordPress admin dashboard and navigate to Plugins > Installed Plugins. Locate WooCommerce and view the version number displayed, or check the plugin header in /wp-content/plugins/woocommerce/woocommerce.phpAffected if The version displayed is between 5.4.0 and 10.5.2 inclusive
-
Verify batch processing is accessibleIn WordPress admin, go to WooCommerce > Settings > Advanced. Look for the Legacy API, REST API, or Batch Processing settings sectionAffected if The batch processing or legacy API endpoints are enabled and accessible to authenticated administrators
-
Confirm the REST API endpoint is reachableSend a GET request to /wp-json/wc/v3/batch or check if the endpoint responds (requires authentication headers from an admin session)Affected if The batch API endpoint returns a valid JSON response rather than a 401/403 error
If the installed WooCommerce version falls within 5.4.0-10.5.2 and the batch processing or legacy API feature is enabled, the environment is vulnerable to the CSRF attack described in this CVE.
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.
dbcve · scopedUpdate WooCommerce to version 10.5.3 or later to obtain the vendor patch; alternatively, disable batch processing functionality until the update can be applied.
Upgrade WooCommerce to the latest available version (currently higher than 10.5.2)
- 1. Backup your WordPress database and files before making any changes
- 2. Navigate to Plugins > Installed Plugins in your WordPress admin dashboard
- 3. Locate WooCommerce in the plugin list
- 4. Check the current installed version to confirm it is between 5.4.0 and 10.5.2
- 5. Click 'Update now' if an update is available, or manually download the latest WooCommerce version from wordpress.org
- 6. After updating, verify the new version is installed (should be higher than 10.5.2)
- 7. Test that the WooCommerce REST API and batch functionality work correctly
- 8. Consider implementing additional CSRF protections at the server level (e.g., ensuring WordPress nonce verification is enforced for all admin actions)
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation2.0 h
- Testing4.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,464.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-3589 — 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-3589 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