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 update functionalities and monitor for unusual update activity.
Description
The Security For WooCommerce WordPress plugin up to version 1.0.16 lacks authorization checks before executing bulk plugin and WordPress core updates. This flaw allows unauthenticated users to trigger the installation of all pending updates on the affected site.