VulnerabilityPublished 11 Nov 2026

CVE-2026-115735: Somatic Framework (WordPress plugin) · External Control of File Name or Path

Affects Somatic Framework (WordPress plugin)Source CVE Database V5

Compare

Not known to be exploited.

Data as of 11 Nov 2026, 06:35 UTC

Severity

High

Rated High by Threat Radar's AI analysis · CVSS not yet scored by NVD

Thin evidence

One scorer or none

Exploitation 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.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponized: A Metasploit exploit module or Exploit-DB entry exists (Metasploit scanner modules do not count), or CISA SSVC or the CVSS exploit maturity reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Affected software

Product	Affected	Fixed in
Somatic Framework	Affected <=1.8.14	Fixed in–

AI-suggested

Users should avoid using affected versions (<=1.8.14) of the Somatic Framework plugin until a fix is released. Restricting plugin usage to trusted users and monitoring for suspicious activity is advised. Check the vendor advisory or plugin repository for updates and apply patches once available.

Description

The Somatic Framework WordPress plugin versions up to 1.8.14 contain a vulnerability where it fails to perform authorization checks or validate user-supplied file paths before deleting files. This flaw allows any authenticated user, including low-privileged roles like subscribers, to delete arbitrary files on the server. Exploitation of this vulnerability can lead to a full site takeover.

Impact

Any authenticated user, including those with subscriber-level access, can delete arbitrary files on the server due to lack of authorization and path validation. This can result in a full site takeover, compromising the integrity and availability of the website and potentially exposing sensitive data or enabling further attacks.

Summary

CVE-2026-115735 is a vulnerability in the Somatic Framework WordPress plugin (<=1.8.14) categorized under CWE-73 (External Control of File Name or Path). The plugin does not verify authorization or validate file paths before deleting files, enabling authenticated users with minimal privileges to delete arbitrary files on the server. This can escalate to a complete compromise of the affected WordPress site.

CWE-73External Control of File Name or Path (opens in a new tab)
Base weaknessLikelihood of exploit: HighOWASP Top 10 A06:2025: Insecure Design (opens in a new tab)
The product allows user input to control or influence paths or file names that are used in filesystem operations.
Architecture and Design
When the set of filenames is limited or known, create a mapping from a set of fixed input values (such as numeric IDs) to the actual filenames, and reject all other inputs. For example, ID 1 could map to "inbox.txt" and ID 2 could map to "profile.txt".
Architecture and Design · Operation
Run your code in a "jail" or similar sandbox environment that enforces strict boundaries between the process and the operating system. This may effectively restrict all access to files within a particular directory.
Architecture and Design
For any security checks that are performed on the client side, ensure that these checks are duplicated on the server side, in order to avoid CWE-602. Attackers can bypass the client-side checks by modifying values after the checks have been performed, or by changing the client to remove the client-side checks…
OWASP Cheat Sheets
XML Security (opens in a new tab)
Mass Assignment (opens in a new tab)
Secure Design Principles (opens in a new tab)
OWASP ASVS 4.0.3
V12.3.2 (opens in a new tab)
V13.3.1 (opens in a new tab)
V5.1.4 (opens in a new tab)
Attack patterns
Subverting Environment Variable Values (opens in a new tab)
Leverage Alternate Encoding (opens in a new tab)
Using Slashes and URL Encoding Combined to Bypass Validation Logic (opens in a new tab)
URL Encoding (opens in a new tab)
Manipulating Web Input to File System Calls (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).

References

wpscan.com/vulnerability/0a43de6d-7b65-4cc6-b02a-479bb79293cc/ (opens in a new tab)

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 11 Nov 2026, 06:35 UTC

WeaknessesCWE-73

Technical details

References

Community reviews

Related threats