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-104448 Overview
CVE-2026-104448 is a Cross-Site Request Forgery (CSRF) vulnerability in YesWiki versions prior to 4.6.7. The flaw resides in the ajaxdeletepage handler, which permanently deletes a page on any GET request carrying a jsonp_callback parameter without verifying a CSRF token. An attacker can lure a logged-in administrator or page owner to a crafted link and trigger deletion of arbitrary pages along with their Access Control Lists (ACLs), links, triples, comments, and referrers. The weakness is tracked as CWE-352: Cross-Site Request Forgery.
Critical Impact
A single victim click on an attacker-controlled link can irreversibly destroy wiki pages and all associated metadata belonging to the targeted site.
Affected Products
- YesWiki versions before 4.6.7
- YesWiki ajaxdeletepage AJAX handler
- Any site relying on YesWiki page ACLs, links, triples, comments, and referrers
Discovery Timeline
- 2026-10-02 - CVE-2026-104448 published to the National Vulnerability Database (NVD)
- 2026-10-02 - Last updated in NVD database
Technical Details for CVE-2026-104448
Vulnerability Analysis
YesWiki exposes an AJAX endpoint, ajaxdeletepage, that removes a wiki page and its associated records. The handler accepts a GET request and, when a jsonp_callback parameter is supplied, executes the deletion branch without checking a CSRF token. Because browsers automatically attach session cookies to GET requests to the YesWiki origin, an authenticated administrator or page owner visiting an attacker-controlled page triggers the deletion under their own privileges.
The deletion cascades across multiple data stores. The handler removes the page content, ACL entries, link records, triples, comments, and referrer metadata. The destructive action is not reversible through the normal wiki revision interface for the deleted ACLs and related tables.
Root Cause
The root cause is missing CSRF protection on a state-changing endpoint, consistent with [CWE-352]. The ajaxdeletepage handler treats the presence of a jsonp_callback query parameter as a legitimate JSONP context and bypasses token validation. State-changing operations should never be exposed via GET and must require a server-verified anti-CSRF token tied to the user session.
Attack Vector
Exploitation is remote and requires user interaction. An attacker crafts an HTML page, email, forum post, or chat message containing a link or embedded resource pointing to the YesWiki ajaxdeletepage handler with a target page name and a jsonp_callback parameter. When a logged-in administrator or page owner loads the attacker's content, the browser issues the authenticated GET request and the server executes the deletion. The attacker needs no credentials and no prior access to the YesWiki instance.
Technical details are documented in the YesWiki GitHub Security Advisory GHSA-hqmg-843g-pp28 and the VulnCheck advisory for CSRF page deletion.
Detection Methods for CVE-2026-104448
Indicators of Compromise
- Web server access logs containing GET requests to the ajaxdeletepage handler that include a jsonp_callback query parameter
- Unexpected page deletions in YesWiki audit records followed by missing ACL, link, triples, comment, or referrer entries for the same page name
- Referer headers on deletion requests pointing to external, untrusted domains or to webmail and chat redirectors
Detection Strategies
- Alert on any request matching the pattern ajaxdeletepage combined with jsonp_callback originating from authenticated administrator or page-owner sessions.
- Correlate deletion events with the HTTP Referer and user session to identify cross-origin initiators that indicate CSRF rather than intentional admin actions.
- Review database change logs for bulk removal of rows across the page, ACL, links, triples, comments, and referrers tables within a short time window.
Monitoring Recommendations
- Forward YesWiki web server and application logs to a centralized logging platform and retain them long enough to investigate retrospective deletions.
- Create a dashboard that tracks daily page deletion counts per user to surface anomalies against baseline administrator activity.
- Monitor outbound links shared with YesWiki administrators through email and collaboration tools for URLs targeting the vulnerable handler.
How to Mitigate CVE-2026-104448
Immediate Actions Required
- Upgrade YesWiki to version 4.6.7 or later on all production and staging instances.
- Restrict administrative and page-owner sessions by requiring recent re-authentication for destructive operations until the upgrade is deployed.
- Audit recent page deletions and restore any pages removed through requests matching the vulnerable pattern.
Patch Information
The YesWiki maintainers released version 4.6.7, which addresses the missing CSRF token check in the ajaxdeletepage handler. Deployment details are available in the YesWiki GitHub Security Advisory GHSA-hqmg-843g-pp28. Apply the upgrade following the vendor's standard update procedure and verify the installed version after deployment.
Workarounds
- Block GET requests to the ajaxdeletepage endpoint at the reverse proxy or Web Application Firewall (WAF), permitting only POST requests with a valid session-bound token.
- Deny any request to ajaxdeletepage that contains a jsonp_callback query parameter at the WAF layer.
- Instruct administrators to use a dedicated browser profile for YesWiki administration and to avoid clicking untrusted links while authenticated.
# Example WAF rule (ModSecurity) to block the vulnerable request pattern
SecRule REQUEST_METHOD "@streq GET" \
"chain,phase:1,deny,status:403,id:1026104448,\
msg:'Block CVE-2026-104448 YesWiki ajaxdeletepage CSRF'"
SecRule REQUEST_URI "@contains ajaxdeletepage" \
"chain"
SecRule ARGS:jsonp_callback "@rx .+"
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

