CVE-2026-32410
Missing Authorization in WBW Currency Switcher for WooCommerce
Publication date: 2026-03-13
Last updated on: 2026-04-29
Assigner: Patchstack
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| wbfactory | woo_currency_switcher | to 2.2.5 (inc) |
| wbw_plugins | wbw_currency_switcher_for_woocommerce | to 2.2.5 (inc) |
Helpful Resources
Exploitability
| CWE ID | Description |
|---|---|
| CWE-862 | The product does not perform an authorization check when an actor attempts to access a resource or perform an action. |
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?
CVE-2026-32410 is a broken access control vulnerability in the WordPress WBW Currency Switcher for WooCommerce plugin versions up to and including 2.2.5.
The issue arises from missing authorization, authentication, or nonce token checks in certain functions, allowing unauthenticated users to perform actions that require higher privileges.
This means that attackers without any prior authentication can exploit the plugin to perform unauthorized actions.
How can this vulnerability impact me? :
The vulnerability allows unauthenticated attackers to perform actions that should require higher privileges, potentially leading to unauthorized changes or manipulations within the WooCommerce currency switcher.
However, the CVSS score of 5.3 indicates a low severity impact, and exploitation is considered unlikely.
Users are advised to update to version 2.2.6 where the issue is resolved to mitigate any risk.
How does this vulnerability affect compliance with common standards and regulations (like GDPR, HIPAA)?:
I don't know
How can this vulnerability be detected on my network or system? Can you suggest some commands?
I don't know
What immediate steps should I take to mitigate this vulnerability?
[{'type': 'paragraph', 'content': 'To mitigate the CVE-2026-32410 vulnerability in the WBW Currency Switcher for WooCommerce plugin, you should update the plugin to version 2.2.6 or later, where the issue is resolved.'}, {'type': 'paragraph', 'content': "Additionally, using services like Patchstack's mitigation tools, which include auto-updates for vulnerable plugins, can help reduce the risk."}] [1]