Skip to main content
Vulnerability Database/CVE-2026-104443

CVE-2026-104443: YesWiki Auth Bypass Vulnerability

CVE-2026-104443 is an authentication bypass flaw in YesWiki that allows authenticated users to delete admin group memberships, causing site-wide lockouts. This post explains its impact, affected versions, and mitigation steps.

Published:

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-104443 Overview

CVE-2026-104443 is a broken access control vulnerability [CWE-863] in YesWiki versions prior to 4.6.7. The flaw resides in the triples delete API, which fails to enforce ownership scope when the filter parameter is empty. Any authenticated user can send a request with an empty filter to delete or forge arbitrary semantic triples. Attackers can abuse this to remove the admins-group membership triple, emptying the admin group and triggering a site-wide authorization lockout. The vulnerability affects the integrity and availability of the wiki, though it does not directly expose confidential data.

Critical Impact

Any authenticated low-privilege user can delete arbitrary semantic triples, including the admins-group membership record, resulting in loss of administrative access across the entire YesWiki instance.

Affected Products

  • YesWiki versions prior to 4.6.7
  • YesWiki triples delete API endpoint
  • Deployments allowing self-registration or any authenticated user accounts

Discovery Timeline

  • 2026-10-02 - CVE-2026-104443 published to the National Vulnerability Database (NVD)
  • 2026-10-02 - Last updated in NVD database

Technical Details for CVE-2026-104443

Vulnerability Analysis

YesWiki stores semantic metadata as triples following a subject-property-value model. The delete API is intended to restrict deletions to triples owned by the requesting user. The authorization scope is applied through a filter parameter supplied with the delete request. When the filter is empty, the scope check is bypassed and the query degrades into an unrestricted delete operation. An authenticated attacker can therefore remove triples belonging to any user, including administrative role assignments.

The most damaging exploitation path targets the triple that defines membership in the admins group. Removing that triple empties the admin group, leaving no account with administrative privileges. The result is a persistent authorization lockout where no user, including the original site owner, can perform administrative actions.

Root Cause

The root cause is incorrect authorization logic [CWE-863] in the triples deletion handler. The code treats an empty filter as a match-all condition instead of rejecting the request or applying a default ownership constraint. Scope enforcement should be mandatory and server-side, independent of client-supplied input.

Attack Vector

Exploitation requires network access to the YesWiki instance and a valid low-privilege user session. The attacker sends an HTTP request to the triples delete endpoint with an empty filter parameter, instructing the server to delete all matching triples without ownership restriction. Attackers can target specific triples such as the admins-group membership to cause an administrative lockout, or forge replacement triples to tamper with site metadata. See the GitHub Security Advisory GHSA-9j7h-ccj2-jxv6 and the VulnCheck Advisory: YesWiki Scope Bypass for additional technical analysis.

No public proof-of-concept exploitation code is referenced in the available advisory data.

Detect Identity Attacks the Moment Authentication Fails

Singularity™ Identity surfaces credential misuse, lateral movement, and privilege escalation in real time, so you can contain the breach before it spreads.

Stop Identity Attacks

Detection Methods for CVE-2026-104443

Indicators of Compromise

  • HTTP requests to the YesWiki triples delete API endpoint containing an empty or missing filter parameter.
  • Sudden removal of entries from the semantic triples table, especially rows referencing admins group membership.
  • Users unexpectedly losing administrative privileges or administrative pages returning authorization errors for all accounts.
  • Unusual triple creation activity from low-privilege accounts shortly after deletion events.

Detection Strategies

  • Enable verbose request logging on the YesWiki application and alert on triples delete API calls that omit the filter parameter or submit empty values.
  • Monitor the triples database table for unexpected deletions of rows where the property corresponds to group membership, particularly the admins group.
  • Correlate authentication logs with triples deletion events to identify low-privilege sessions issuing admin-impacting requests.

Monitoring Recommendations

  • Capture YesWiki web server access logs centrally and retain them for forensic review of triples API usage.
  • Alert on administrative role changes that occur outside of expected administrator sessions.
  • Baseline normal triples delete API traffic to detect anomalous volume or unusual filter patterns from authenticated users.

How to Mitigate CVE-2026-104443

Immediate Actions Required

  • Upgrade all YesWiki installations to version 4.6.7 or later without delay.
  • Audit the triples table and verify that admins-group membership entries are intact and reference legitimate accounts.
  • Review authentication logs and triples API traffic for signs of exploitation prior to patching.
  • Restrict self-registration temporarily if the instance exposes account creation to untrusted users.

Patch Information

YesWiki version 4.6.7 remediates the empty-filter scope bypass by enforcing ownership checks in the triples delete handler regardless of filter contents. Review the vendor's GitHub Security Advisory GHSA-9j7h-ccj2-jxv6 for the fix commit and upgrade guidance.

Workarounds

  • If patching cannot be performed immediately, disable or firewall the triples delete API endpoint at the web server or reverse proxy layer.
  • Limit access to the YesWiki instance to trusted authenticated users through network ACLs or VPN until the upgrade is applied.
  • Create periodic backups of the YesWiki database so that deleted admins-group triples can be restored quickly after an incident.
bash
# Example reverse proxy rule to block empty-filter triples delete requests until patched
location ~ ^/\?api/triples {
    if ($request_method = DELETE) {
        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

Experience the Most Advanced Cybersecurity Platform

See how the world’s most intelligent, autonomous cybersecurity platform can protect your organization today and into the future.