Hide Category by User Role for WooCommerce <= 2.3.1 - Missing Authorization to Unauthenticated Cache Flushing
Strategic Overview
- Status
- Patched in 2.3.2
- Affected Plugin
- Hide Category by User Role for WooCommerce
- Affected Version
<= 2.3.1- CVSS
- 5.3Medium
- Weakness type
- CWE-862 · Missing Authorization
- CVE
CVE-2025-13441
At a glance
CVE-2025-13441 is a medium-severity Missing Authorization vulnerability in the Hide Category by User Role for WooCommerce WordPress plugin, affecting versions <= 2.3.1. It carries a CVSS score of 5.3 (reachable over the network; low attack complexity). Exploitation requires no authentication. The issue is fixed in version 2.3.2; sites on affected versions should update now. Disclosed November 2025, reported by Legion Hunter.
Vulnerability Overview
The Hide Category by User Role for WooCommerce plugin for WordPress is vulnerable to Missing Authorization in all versions up to, and including, 2.3.1. This is due to a missing capability check on the admin_init hook that executes wp_cache_flush(). This makes it possible for unauthenticated attackers to flush the site's object cache via forged requests, potentially degrading site performance.
Technical Analysis
The vector marks this flaw as remotely reachable over the network, with low attack complexity — no special timing or configuration is needed, and no privileges on the target site, and no interaction from a victim user.
CWE-862: Missing Authorization
Hide Category by User Role for WooCommerce <= 2.3.1 carries this weakness at wp_cache_flush(), and reaching it takes no account at all. A missing authorization check means a function is reachable by anyone who can reach the endpoint, because the code never asks whether the caller is allowed to perform the action.
Any user who can reach the endpoint gets to run an action reserved for higher-privileged roles, from reading protected data to changing settings or content. For Hide Category by User Role for WooCommerce the fix is 2.3.2: builds <= 2.3.1 are affected, anything from 2.3.2 onward is not.
Remediation
Update to version 2.3.2, or a newer patched version
How does WordSec protect against this?
This one needs no account at all, which puts it outside what login hardening can reach; WordSec's login security narrows the account-level paths around it, and the firewall is what inspects the request itself. None of that substitutes for the fix: Hide Category by User Role for WooCommerce 2.3.2 closes this, and updating the plugin is the step that ends it.
- Login Security
- Alerts
External References
Related records
Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C