SECURITY FOR WOOCOMMERCE · CVE-2026-123699 · Package
NO FIX YET · SEE WHAT TO DO
The Security For WooCommerce plugin (slug ultimate-security-for-woocommerce) up to 1.0.16 does not check authorisation before running bulk updates. An unauthenticated visitor can force every pending plugin, theme and WordPress core update to be installed. WPScan lists no known fix. Per WPScan the flaw is limited to forced updates, one of 10 separate unauthenticated flaws in the same plugin.
first public Nov 9, 2026 · 2 sources
Could this affect your app?
Free first check from your website. Connect your repo for the full answer.
Any WordPress/WooCommerce site with the Security For WooCommerce plugin (ultimate-security-for-woocommerce) at 1.0.16 or earlier. No login is needed, so an installed plugin means exposure. The effect is that a visitor can trigger installation of pending updates, which can break the site or cause unplanned upgrades. Sites without the plugin can skip it.
Not affected if plugin-not-installed
Who cares self-hosted, woocommerce, wordpress
1.0.16 or lower is affectedNo known fix)Posts 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 check that the requester is authorised before running bulk Security For WooCommerce WordPress plugin through 1.0.16, and WordPress core updates, allowing unauthenticated users to force every pending update to be installed on the site.
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.