Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.
Sources: National Vulnerability Database, CISA KEV, Exploit-DB
CVE-2026-104452 Overview
CVE-2026-104452 is a Cross-Site Request Forgery (CSRF) vulnerability in YesWiki versions before 4.6.7. The flaw resides in the filemanager page handler, which processes attachment deletion requests over HTTP GET without validating a CSRF token. An attacker who tricks an authenticated page owner or administrator into visiting a crafted link can delete or permanently purge page attachments. The vulnerability is tracked under CWE-352 and documented in GitHub Security Advisory GHSA-7m4h-m7qm-hc32.
Critical Impact
A single click on a malicious link by a logged-in YesWiki administrator can erase or permanently purge page attachments without further interaction.
Affected Products
- YesWiki versions prior to 4.6.7
- YesWiki filemanager page handler
- Deployments exposing authenticated administrative sessions to untrusted browsing contexts
Discovery Timeline
- 2026-10-02 - CVE-2026-104452 published to the National Vulnerability Database (NVD)
- 2026-10-02 - Last updated in NVD database
Technical Details for CVE-2026-104452
Vulnerability Analysis
The YesWiki filemanager handler accepts destructive operations through HTTP GET requests. Supported actions include do=del, do=erase, and do=emptytrash. These operations modify server-side state by removing or purging page attachments. The handler does not verify a CSRF token or require a POST request before executing the deletion. As a result, any authenticated user who navigates to an attacker-controlled URL triggers the operation under their own session.
Because the destructive endpoint is reachable via a top-level GET navigation, attackers can embed the payload in an <a href> link, an <img src> tag, or an auto-redirecting page. The browser automatically attaches the victim's YesWiki session cookies, satisfying the authorization check.
Root Cause
The root cause is missing anti-CSRF enforcement on a state-changing endpoint, combined with the use of GET as the HTTP method for destructive actions. This pattern violates the principle that safe HTTP methods must not alter server state. The filemanager handler trusts the presence of a valid session cookie as sufficient authorization, which is the defining weakness captured by CWE-352.
Attack Vector
Exploitation requires user interaction from a logged-in page owner or administrator. The attacker crafts a URL targeting the YesWiki instance with do=del, do=erase, or do=emptytrash parameters pointing at a specific page. The attacker then delivers the link through phishing email, forum posts, chat messages, or embedded resources on third-party sites. When the victim loads the link in a browser carrying an authenticated YesWiki session, the server executes the attachment deletion. The emptytrash variant results in permanent data loss because it bypasses recoverable soft-deletion. See the VulnCheck Advisory on YesWiki CSRF for additional detail.
Detection Methods for CVE-2026-104452
Indicators of Compromise
- Web server access logs showing GET requests to the filemanager handler containing do=del, do=erase, or do=emptytrash parameters
- HTTP Referer headers on destructive YesWiki requests pointing to external or unrelated domains
- Unexpected attachment deletion events in YesWiki audit logs correlated with administrator browsing sessions
Detection Strategies
- Alert on YesWiki HTTP requests where the do parameter indicates a destructive action but the HTTP method is GET
- Correlate attachment deletion events with the originating Referer and User-Agent to identify out-of-band triggers
- Review web application firewall (WAF) logs for filemanager endpoint access patterns inconsistent with normal administrator workflows
Monitoring Recommendations
- Enable verbose request logging on the YesWiki filemanager route and forward logs to a centralized analytics platform
- Baseline normal administrator attachment-management activity and alert on deviations such as off-hours deletions
- Monitor for repeated GET requests to the deletion endpoint from a single session, which may indicate scripted CSRF payloads
How to Mitigate CVE-2026-104452
Immediate Actions Required
- Upgrade YesWiki to version 4.6.7 or later, which introduces CSRF token validation on the filemanager handler
- Audit existing page attachments against known-good backups to identify any unauthorized deletions
- Instruct administrators and page owners to log out of YesWiki when not actively using the application
Patch Information
The YesWiki maintainers resolved the issue in version 4.6.7. Refer to GitHub Security Advisory GHSA-7m4h-m7qm-hc32 for upgrade instructions and the specific commit addressing the missing CSRF token validation in the filemanager page handler.
Workarounds
- Restrict access to the YesWiki instance using network-level controls such as IP allowlisting or VPN-only access until patching is complete
- Configure the YesWiki session cookie with SameSite=Strict or SameSite=Lax to reduce cross-site request risk
- Deploy a WAF rule to block GET requests to the filemanager handler containing do=del, do=erase, or do=emptytrash parameters
# Example WAF rule concept (ModSecurity-style) to block destructive GET requests
SecRule REQUEST_METHOD "@streq GET" \
"chain,id:1026104452,phase:1,deny,status:403,msg:'YesWiki CSRF deletion attempt'"
SecRule REQUEST_URI "@contains filemanager" "chain"
SecRule ARGS:do "@rx ^(del|erase|emptytrash)$"
Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.
Sources: National Vulnerability Database, CISA KEV, Exploit-DB

