GHSA-6x7x-gcmf-7r8x: YesWiki vulnerable to unauthenticated arbitrary page deletion via `{{erasespamedcomments}}` action
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.
AI Analysis
Technical Summary
The vulnerability in YesWiki (CVE-2026-52766) involves the erasespamedcomments action (actions/EraseSpamedCommentsAction.php), which processes a POSTed suppr[] array to delete wiki pages without any authorization or CSRF checks. The default ACL configuration grants write access to all users, including anonymous, enabling exploitation on fresh installs. The deletion functions PageController::delete() and PageManager::deleteOrphaned() do not verify user permissions or whether pages are orphaned, allowing unconditional deletion of pages and related database entries. This results in arbitrary page deletion, including critical pages such as the front page and admin pages.
Potential Impact
An attacker with write access (default for all users on fresh installs) can delete any wiki page without authorization, leading to loss of content including front page and administrative pages. This compromises the integrity and availability of the wiki content. The vulnerability does not affect confidentiality but results in high impact on integrity and availability.
Mitigation Recommendations
Patch status is not yet confirmed — check the vendor advisory for current remediation guidance. Until a fix is available, 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.
GHSA-6x7x-gcmf-7r8x: YesWiki vulnerable to unauthenticated arbitrary page deletion via `{{erasespamedcomments}}` action
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.
CVSS v3.1
Affected software
Run on your own infrastructure? Check whether these packages are installed with threat-finder — our free open-source scanner.
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
The vulnerability in YesWiki (CVE-2026-52766) involves the erasespamedcomments action (actions/EraseSpamedCommentsAction.php), which processes a POSTed suppr[] array to delete wiki pages without any authorization or CSRF checks. The default ACL configuration grants write access to all users, including anonymous, enabling exploitation on fresh installs. The deletion functions PageController::delete() and PageManager::deleteOrphaned() do not verify user permissions or whether pages are orphaned, allowing unconditional deletion of pages and related database entries. This results in arbitrary page deletion, including critical pages such as the front page and admin pages.
Potential Impact
An attacker with write access (default for all users on fresh installs) can delete any wiki page without authorization, leading to loss of content including front page and administrative pages. This compromises the integrity and availability of the wiki content. The vulnerability does not affect confidentiality but results in high impact on integrity and availability.
Mitigation Recommendations
Patch status is not yet confirmed — check the vendor advisory for current remediation guidance. Until a fix is available, 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.
Technical Details
- Gcve Source
- db.gcve.eu
- Osv Id
- GHSA-6x7x-gcmf-7r8x
- Osv Schema Version
- 1.4.0
- Aliases
- ["CVE-2026-52766"]
- Ecosystems
- ["Packagist"]
- Database Specific Severity
- CRITICAL
- Cvss Version
- 3.1
Threat ID: 6a50ba7468715ace4358034e
Added to database: 07/10/2026, 09:25:08 UTC
Last enriched: 07/10/2026, 09:56:26 UTC
Last updated: 07/10/2026, 11:16:43 UTC
Views: 4
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.