ULTIMATE-SECURITY-FOR-WOOCOMMERCE · CVE-2026-123698 · Package
NO FIX YET · SEE WHAT TO DO
WPScan reports that the Security For WooCommerce plugin (WordPress.org slug ultimate-security-for-woocommerce), versions up to and including 1.0.16, does not restrict access to one of its REST API routes. Unauthenticated users can retrieve its full settings, including configured secret keys and the hidden login URL. WPScan lists no known fix. The exact route is not published; WPScan will show the PoC on 2026-11-23. CVSS 5.3 (medium), CWE-862.
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.
Sites running the Security For WooCommerce WordPress plugin at version 1.0.16 or earlier are exposed, since the flawed REST route answers without authentication. Sites without the plugin, or running a later version, are not affected per the sources. The sources do not state a fixed version or a workaround.
Not affected if plugin-not-installed
Who cares security-for-woocommerce, woocommerce, wordpress
1.0.16 or earlier: WordPress admin > Plugins, or run wp plugin get ultimate-security-for-woocommerceNo 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 restrict access to one of its REST API routes, allowing unauthenticated users to retrieve its full settings, including configured secret keys and the hidden login URL.
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.