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-104447 Overview
CVE-2026-104447 is a cross-site request forgery (CSRF) vulnerability [CWE-352] affecting YesWiki versions prior to 4.6.7. The flaw resides in the autoupdateUpdateAction handler, which processes package deletion requests without validating request origin or anti-CSRF tokens. An attacker who tricks an authenticated administrator into visiting a crafted link can invoke action=delete with a package parameter to remove installed extensions. Removing core packages such as bazar breaks site functionality and can disable features that other components depend on.
Critical Impact
An attacker-controlled link visited by a logged-in YesWiki administrator can silently delete installed packages, including core extensions, degrading or disabling the wiki.
Affected Products
- YesWiki versions prior to 4.6.7
- Deployments exposing the autoupdate module to authenticated administrators
- Sites relying on packaged extensions such as bazar for core functionality
Discovery Timeline
- 2026-10-02 - CVE-2026-104447 published to NVD
- 2026-10-02 - Last updated in NVD database
Technical Details for CVE-2026-104447
Vulnerability Analysis
The vulnerability affects the YesWiki autoupdate component that manages installation and removal of extension packages. The UpdateAction handler accepts package management operations through HTTP GET requests without verifying that the request originated from a legitimate session context. Because the destructive action=delete operation is reachable via a simple URL, any mechanism that forces a browser to issue the request completes the deletion when an administrator session is active.
The affected endpoint accepts the operation and target through query parameters such as action=delete and package=<name>. Supplying the name of an installed package removes it from the YesWiki instance. Deleting bazar or similar foundational extensions breaks dependent features across the site.
Root Cause
The root cause is missing CSRF protection on a state-changing endpoint, matching [CWE-352]. The UpdateAction handler does not require a per-session anti-CSRF token and does not restrict the delete operation to POST with origin validation. Server-side authorization checks confirm that the requester is authenticated, but authentication alone cannot distinguish an intentional administrative action from a forged request initiated by an attacker-controlled page.
Attack Vector
Exploitation requires an attacker to lure an authenticated YesWiki administrator to a page they control, such as a phishing email link, a comment on another site, or a malicious advertisement. The attacker page issues a GET request to the target YesWiki instance with action=delete and the chosen package parameter. The browser automatically attaches the administrator's session cookie, and the server executes the deletion. No prior interaction with the attacker is required beyond following the crafted link while logged in.
See the GitHub Security Advisory GHSA-jp5c-grgj-624x and the Vulncheck Advisory for additional technical context.
Detection Methods for CVE-2026-104447
Indicators of Compromise
- Web server access logs containing GET requests to the YesWiki autoupdate endpoint with action=delete and a package query parameter.
- Requests to the autoupdate handler with Referer headers pointing to external or unexpected domains.
- Unexpected removal of installed extensions, particularly bazar, resulting in broken wiki features or 500-series errors.
Detection Strategies
- Alert on any request to the autoupdateUpdateAction endpoint that uses the HTTP GET method combined with a destructive action value.
- Correlate administrator session identifiers with the originating Referer and Origin headers to identify cross-origin invocations of sensitive endpoints.
- Review YesWiki application logs for package removal events that are not preceded by administrator actions in the management UI.
Monitoring Recommendations
- Monitor the filesystem path containing YesWiki extensions for unexpected deletions of package directories.
- Track administrator login sessions and correlate them with subsequent autoupdate activity to surface anomalies.
- Forward web server and application logs to a central analytics platform and build detections for the specific query string pattern associated with package deletion.
How to Mitigate CVE-2026-104447
Immediate Actions Required
- Upgrade YesWiki to version 4.6.7 or later, which addresses the missing CSRF protection in the autoupdateUpdateAction handler.
- Instruct administrators to log out of YesWiki sessions when not actively managing the site to reduce the window of exposure.
- Restrict administrative access to trusted networks or VPN segments while patching is completed.
Patch Information
The fix is included in YesWiki 4.6.7. Refer to the GitHub Security Advisory GHSA-jp5c-grgj-624x for the authoritative patch details and affected version range.
Workarounds
- Place the YesWiki administrative interface behind an authenticating reverse proxy that enforces origin and referer checks on state-changing requests.
- Use a web application firewall rule to block GET requests to the autoupdate endpoint carrying action=delete.
- Require administrators to use a dedicated browser profile for YesWiki management to limit exposure to third-party pages that could issue forged requests.
# Example WAF rule concept: block GET requests invoking package deletion
# via the YesWiki autoupdate handler
SecRule REQUEST_METHOD "@streq GET" \
"chain,deny,status:403,id:1026104447,msg:'YesWiki CSRF package deletion attempt'"
SecRule REQUEST_URI "@rx (?i)autoupdate.*action=delete.*package=" "t:none"
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

