The Security For WooCommerce WordPress plugin through 1.0.16 does not restrict who can request a user's current
Source GCVE Database
Not known to be exploited.
Data as of 11 Nov 2026, 07:32 UTC
Rated High by Threat Radar's AI analysis · CVSS not yet scored by NVD
Thin evidence
One scorer or noneExploitation evidence
Disclosed: evidence found.
CVE published 11 Nov 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 10 Nov 2026.
What to do
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| Security For WooCommerce | Affected
| Fixed in– |
AI-suggested
Until a fix is available, consider disabling the plugin or the affected 2FA functionality to prevent exploitation.
Description
The Security For WooCommerce WordPress plugin up to version 1.0.16 has a vulnerability that allows unauthenticated users to request and obtain a user's current two-factor authentication (2FA) code or secret. This flaw enables attackers to bypass the second factor of authentication on sites using this plugin's one-time password library.