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-104451 Overview
CVE-2026-104451 is a Cross-Site Request Forgery (CSRF) vulnerability [CWE-352] in YesWiki versions before 4.6.7. The flaw resides in the RevisionsHandler component, which processes revision restoration through GET requests without validating a CSRF token. An attacker can craft a malicious link containing the restoreRevisionId parameter and lure a write-capable user into following it. The target's browser silently issues the authenticated request, overwriting current page content with a stale or vandalized revision. Successful exploitation damages wiki content integrity without triggering authentication prompts or user confirmation.
Critical Impact
Attackers can silently replace live YesWiki pages with older or vandalized revisions when authenticated editors are tricked into clicking a crafted link.
Affected Products
- YesWiki versions prior to 4.6.7
- Deployments exposing the RevisionsHandler endpoint to authenticated editors
- Any YesWiki instance accessible to users with write permissions
Discovery Timeline
- 2026-10-02 - CVE-2026-104451 published to the National Vulnerability Database (NVD)
- 2026-10-02 - Last updated in NVD database
Technical Details for CVE-2026-104451
Vulnerability Analysis
The vulnerability is a server-side state-change operation triggered via a GET request without anti-CSRF protections. YesWiki's RevisionsHandler accepts a restoreRevisionId parameter and executes the revision rollback using only the victim's ambient session credentials. Because the handler does not validate an origin-bound token or require a POST with a verifiable nonce, any cross-origin page can initiate the restoration. The attack requires a victim with write privileges to visit a crafted URL during an authenticated YesWiki session. The impact is limited to integrity of wiki content, with no direct confidentiality or availability consequences.
Root Cause
The root cause is missing CSRF token validation on a state-changing endpoint. RevisionsHandler treats an authenticated GET request as sufficient authorization to overwrite a page with a prior revision. The handler also violates the HTTP semantic principle that GET requests should be safe and idempotent.
Attack Vector
Exploitation requires network access to the YesWiki instance and user interaction from a victim with write permissions. The attacker hosts a page containing an image tag, iframe, or top-level navigation targeting the YesWiki URL with a crafted restoreRevisionId value. When the victim loads the attacker-controlled resource while logged in, the browser attaches session cookies and the revision is restored on the server. No credential theft or privilege escalation is required.
For technical details of the fix, refer to the GitHub Security Advisory GHSA-vj5g-974q-7ff3 and the VulnCheck Advisory for YesWiki CSRF.
Detection Methods for CVE-2026-104451
Indicators of Compromise
- Web server access logs showing GET requests containing the restoreRevisionId parameter originating from external Referer headers.
- Unexpected revision restoration events in YesWiki page history for pages that users did not intentionally edit.
- Clusters of revision rollbacks performed by multiple accounts within a short window following distribution of a phishing lure.
Detection Strategies
- Alert on HTTP requests to RevisionsHandler endpoints where the Referer header is absent or references an external origin.
- Correlate wiki revision history changes with user browsing telemetry to identify restorations occurring without a preceding editor view of the revision page.
- Hunt for inbound links in email, chat, or forum platforms that embed YesWiki URLs with the restoreRevisionId query parameter.
Monitoring Recommendations
- Enable detailed access logging on the YesWiki web server and retain logs for post-incident revision analysis.
- Monitor the YesWiki audit trail for rollback actions attributed to editors who did not intend to perform them.
- Track outbound requests from user workstations to known YesWiki hostnames with suspicious query parameters.
How to Mitigate CVE-2026-104451
Immediate Actions Required
- Upgrade all YesWiki instances to version 4.6.7 or later, which introduces CSRF token validation in RevisionsHandler.
- Audit page revision history for unexpected restorations since the vulnerability window and roll forward affected content.
- Communicate the risk to editors and remind write-capable users to avoid clicking untrusted links while authenticated.
Patch Information
The fix is included in YesWiki 4.6.7. Administrators should review the GitHub Security Advisory GHSA-vj5g-974q-7ff3 for the complete remediation details and apply the upgrade through standard YesWiki update procedures.
Workarounds
- Place the YesWiki instance behind a reverse proxy or web application firewall that strips or blocks GET requests containing the restoreRevisionId parameter from external referrers.
- Enforce SameSite=Strict or SameSite=Lax attributes on YesWiki session cookies to limit cross-origin credential attachment until the upgrade is applied.
- Temporarily restrict write permissions to a minimal set of trusted editors to reduce the pool of exploitable sessions.
# Example reverse proxy rule (nginx) to block external referrer rollback attempts
if ($arg_restoreRevisionId) {
if ($http_referer !~* "^https?://yeswiki\.example\.com") {
return 403;
}
}
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

