CVE-2026-52766: yeswiki/yeswiki · YesWiki vulnerable to unauthenticated arbitrary page deletion via `{{erasespamedcomments}}` action
Affects yeswiki/yeswikiSource GCVE Database
Not known to be exploited · CVSS 9.1 Critical : upgrade to 4.6.6 as a priority.
Data as of 30 Oct 2026, 06:59 UTC
- EPSS
- 0.5% chance of exploitation in 30 days – higher than 47% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in 4.6.6
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:HExploitation evidence
Disclosed: evidence found.
CVE published 9 Jul 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 29 Oct 2026.
What to do
Upgrade yeswiki/yeswiki to 4.6.6.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| Packagistyeswiki/yeswiki | Affected
| Fixed in
|
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
If you cannot patch yet, administrators should restrict write access by configuring the permissions to disallow anonymous or unauthorized users from performing write actions, especially the erasespamedcomments action. Implementing proper authorization checks and CSRF protections on the erasespamedcomments action is necessary to prevent exploitation.
Description
YesWiki versions prior to 4.6.6 contain a critical vulnerability in the erasespamedcomments action that allows unauthenticated users with default write access to delete arbitrary wiki pages without authorization checks. The vulnerability arises from the lack of access control on the {{erasespamedcomments}} action, combined with the default permissive ACL configuration and the absence of validation in the page deletion functions. This permits deletion of any page, including the front page and administrative pages, by sending crafted POST requests. No CSRF protections or per-page authorization checks are performed during deletion.