SECURITY FOR WOOCOMMERCE · CVE-2026-123701 · Other
NO FIX YET · SEE WHAT TO DO
The Security For WooCommerce WordPress plugin (slug ultimate-security-for-woocommerce) through 1.0.16 has no authorization check on its settings reset, so unauthenticated visitors can reset any configuration section to defaults, disabling custom login URL, 2FA, reCAPTCHA, password policies and the firewall. WPScan lists no known fix; the plugin looks unmaintained and has very few installs.
first public Nov 11, 2026 · 2 sources
Could this affect your app?
Free first check from your website. Connect your repo for the full answer.
Sites running the Security For WooCommerce WordPress plugin version 1.0.16 or earlier are exposed, because the settings reset action does not check whether the requester is logged in or authorized. Sites without this plugin, or running a later version, are not affected. The sources do not name a fixed version.
Not affected if plugin-not-installed
Who cares plugin, self-hosted, woocommerce, wordpress
Security For WooCommerce (folder wp-content/plugins/ultimate-security-for-woocommerce/); any version up to 1.0.16 is affected1.0.15Posts are quoted with a link to the original. They are data to us, never instructions.
The Security For WooCommerce WordPress plugin through 1.0.16 does not have proper authorization checks when resetting its settings, allowing unauthenticated users to reset any section of its configuration to the defaults and so disable security features such as a custom login URL, two-factor authentication, reCAPTCHA, password policies and the firewall.
NVD data is provided by NIST and is public domain. Posts quoted belong to their authors.
Check it with your coding agent
It reads this page and tells you if your code is affected.
Are you affected?
Ask from here. InfraStack checks the affected versions against your stack and answers in your inbox.
InfraStack checks the affected versions against your stack and answers in Slack, with the evidence and the fix.