The Security For WooCommerce WordPress plugin through 1.0.16 does not check that the requester is authorised before
Source GCVE Database
Not known to be exploited.
Data as of 11 Nov 2026, 07:20 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, restrict access to the plugin's functionality to trusted users only and monitor for unusual activity related to secret key regeneration.
Description
The Security For WooCommerce WordPress plugin through version 1.0.16 has a vulnerability where it does not verify if the requester is authorized before regenerating secret keys and salts in the site's configuration file. This flaw allows unauthenticated users to log out every user on the site. Additionally, on servers that cannot reach the WordPress.org API, this can corrupt the configuration file and take the entire site offline.