SECURITY FOR WOOCOMMERCE · CVE-2026-123697 · Other
NO FIX YET · SEE WHAT TO DO
The Security For WooCommerce WordPress plugin through 1.0.16 lets unauthenticated visitors request any user's current two-factor code or two-factor secret. An attacker who gets these can log in as that account and bypass the second factor.
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 running the Security For WooCommerce plugin version 1.0.16 or earlier, using its two-factor login. An unauthenticated visitor can request any account's current 2FA code or secret and so skip the second factor, on sites where the plugin's one-time password library is available. Sites without the plugin, or that use a different 2FA plugin, can skip it.
Not affected if plugin-newer-than-1.0.16, plugin-not-installed, two-factor-feature-unused
Who cares no-fix, two-factor-auth, woocommerce, wordpress, wordpress-plugin
1.0.16Posts 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 who can request a user's current two-factor code or two-factor secret, allowing unauthenticated users to obtain them for any account and bypass the second factor on sites where its one-time password library is available.
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.