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-104453 Overview
CVE-2026-104453 is a Cross-Site Request Forgery (CSRF) vulnerability [CWE-352] affecting YesWiki versions before 4.6.7. The flaw resides in the admintag action, which processes tag deletion through unauthenticated GET requests. Attackers can craft malicious links that, when clicked by an authenticated administrator, trigger bulk deletion of tag triples from the wiki. The delete_tag parameter accepts a wide id range, enabling attackers to purge large sets of tag associations in a single request. Because the admin session cookie uses SameSite=Lax, top-level navigation to the attacker-controlled URL carries the cookie and authorizes the destructive action.
Critical Impact
Administrators who follow attacker-crafted links can inadvertently delete bulk tag associations across the YesWiki instance, degrading content integrity and site taxonomy.
Affected Products
- YesWiki versions prior to 4.6.7
- YesWiki admintag action handler
- YesWiki deployments relying on default SameSite=Lax session cookies
Discovery Timeline
- 2026-10-02 - CVE-2026-104453 published to NVD
- 2026-10-06 - Last updated in NVD database
Technical Details for CVE-2026-104453
Vulnerability Analysis
The vulnerability stems from YesWiki's admintag action accepting state-changing requests over HTTP GET without CSRF token validation. An attacker constructs a URL that targets the admin tag management endpoint and specifies a delete_tag parameter containing a wide id range. When an authenticated administrator visits a page or link controlled by the attacker, the browser performs top-level navigation to the YesWiki host. Because the administrator's session cookie is scoped as SameSite=Lax, the browser attaches it to the GET request. YesWiki then processes the request as a legitimate administrative action and deletes the matching tag triples.
The impact is limited to integrity and availability of tag data. Confidentiality is not affected, since the action does not return sensitive content to the attacker. User interaction is required because the administrator must click or be redirected to the malicious link.
Root Cause
The root cause is the absence of anti-CSRF controls on the admintag action in YesWiki releases prior to 4.6.7. The handler accepts administrative state changes via GET and does not require a per-request nonce, origin check, or SameSite=Strict cookie policy. Combined with a parameter design that accepts broad id ranges, a single crafted request can affect many records.
Attack Vector
Exploitation requires an attacker to deliver a crafted URL to an authenticated YesWiki administrator through email, chat, a third-party site, or embedded link. When the administrator navigates to the URL, the browser issues a GET to the YesWiki admintag endpoint with the delete_tag parameter containing the attacker-chosen id range. The admin session cookie is sent automatically, and the server executes the deletion. See the GitHub Security Advisory GHSA-5c27-6gcm-hc7x and the VulnCheck Advisory for YesWiki CSRF for technical details.
Detection Methods for CVE-2026-104453
Indicators of Compromise
- Unexpected GET requests to the YesWiki admintag endpoint containing a delete_tag parameter with a wide numeric id range.
- HTTP Referer headers on admin actions pointing to external, untrusted domains.
- Sudden, large-scale removal of tag triples recorded in YesWiki audit or database logs.
Detection Strategies
- Review web server access logs for GET requests to the admintag action issued by administrator sessions with external referrers.
- Baseline normal administrator activity on tag management endpoints and alert on volume spikes in delete_tag operations.
- Correlate authenticated admin session identifiers with destructive tag operations originating from off-site navigation.
Monitoring Recommendations
- Enable verbose logging on YesWiki administrative actions and ship logs to a centralized SIEM for retention and analysis.
- Monitor for anomalous bursts of database DELETE statements against the YesWiki tag table.
- Alert on administrator browser sessions following links from untrusted referrers to administrative endpoints.
How to Mitigate CVE-2026-104453
Immediate Actions Required
- Upgrade YesWiki to version 4.6.7 or later, which addresses the CSRF flaw in the admintag action.
- Instruct administrators to log out of YesWiki when not actively managing the site to reduce the session window.
- Audit recent tag deletion activity and restore removed tag triples from backups if unauthorized deletions are found.
Patch Information
The YesWiki project resolved the issue in release 4.6.7. Operators should apply the upstream update as documented in the GitHub Security Advisory GHSA-5c27-6gcm-hc7x.
Workarounds
- Place the YesWiki admin interface behind an authenticated reverse proxy or VPN to reduce exposure to cross-site navigation.
- Configure session cookies with SameSite=Strict where supported, so cross-site top-level navigation does not carry admin credentials.
- Restrict administrator browsers from loading untrusted external content while an administrative session is active.
# Configuration example
# Upgrade YesWiki to a fixed release
git -C /var/www/yeswiki fetch --tags
git -C /var/www/yeswiki checkout 4.6.7
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

