The Somatic Framework WordPress plugin through 1.8.14 does not perform an authorization check or validate a
Source GCVE Database
Not known to be exploited.
Data as of 11 Nov 2026, 07:47 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 |
|---|---|---|
| Somatic Framework | Affected
| Fixed in– |
AI-suggested
Until a fix is available, restrict authenticated user roles to trusted users only and monitor for suspicious activity related to file deletions.
Description
The Somatic Framework WordPress plugin versions up to 1.8.14 contain a vulnerability where no authorization check or validation of user-supplied file paths is performed before deleting files. This flaw allows any authenticated user, including low-privileged roles such as subscribers, to delete arbitrary files on the server. Exploitation of this vulnerability can lead to a full site takeover.