CVE-2025-12835: WooMulti (WordPress plugin) · Path Traversal
Affects WooMulti (WordPress plugin)Source CVE Database V5
Not known to be exploited · CVSS 7.3 High.
Data as of 26 Oct 2026, 06:26 UTC
- EPSS
- 0.2% chance of exploitation in 30 days – higher than 21% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:U/C:N/I:H/A:HExploitation evidence
Disclosed: evidence found.
CVE published 12 Dec 2025
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: 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 2026-10-26.
What to do
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| WooMulti | Affected
| Fixed in– |
AI-suggested
European organizations should immediately restrict access to the WooMulti plugin features, especially file deletion functionalities, limiting them to trusted administrators only. Implement strict role-based access controls to prevent low-privilege users from performing sensitive operations. Monitor server logs for unusual file deletion activities and set up alerts for suspicious behavior. Employ web application firewalls (WAFs) with custom rules to detect and block path traversal attempts targeting the 'file' parameter. Regularly back up website files and databases to enable rapid recovery in case of file deletion attacks. Engage with the plugin vendor or community for updates and apply patches promptly once available. Conduct security audits and penetration testing focused on plugin vulnerabilities to identify and remediate similar issues proactively.
Description
The WooMulti WordPress plugin through 17 does not validate a file parameter when deleting files, which could allow any authenticated users, such as subscriber to delete arbitrary files on the server.