CVE-2026-104444
Deferred Deferred - Pending Action

Authorization Bypass in YesWiki via Comments API

Publication date: 2026-10-02

Last updated on: 2026-10-02

Assigner: VulnCheck

Description
YesWiki before 4.6.7 contains an authorization bypass vulnerability in the comments API editComment route that allows authenticated low-privilege users to overwrite arbitrary pages or comments by supplying their own page as the pagetag field. Attackers can send a POST request to the api/comments endpoint targeting a victim tag, bypassing per-page write ACLs to replace content and reparent existing pages or comments.

CVSS Scores

EPSS Scores

Probability:
Percentile:

Meta Information

Published
2026-10-02
Last Modified
2026-10-02
Generated
2026-10-02
AI Q&A
2026-10-02
EPSS Evaluated
N/A
NVD
CVE-2026-104444
EUVD
EUVD-2026-91455

Affected Vendors & Products

Showing 1 associated CPE
Vendor Product Version / Range
yeswiki yeswiki to 4.6.7 (exc)

Helpful Resources

Exploitability

CWE
CWE Icon
KEV
KEV Icon
CWE ID Description
CWE-639 The system's authorization functionality does not prevent one user from gaining access to another user's data or record by modifying the key value identifying the data.

Attack-Flow Graph

AI Quick Actions

Instant insights powered by AI
Executive Summary

CVE-2026-104444 is an authorization bypass flaw in YesWiki versions up to 4.6.6. It allows authenticated low-privilege users to overwrite arbitrary pages or comments by exploiting the Comments API's editComment route. The vulnerability occurs because the pagetag field in POST requests is used for authorization checks instead of validating the target tag being modified, bypassing write ACLs.

Detection Guidance

Check YesWiki versions prior to 4.6.7 by running: grep -r 'version' /path/to/yeswiki/config or check the admin panel. Monitor POST requests to api/comments with pagetag fields not matching the target tag. Look for unauthorized page modifications or comment edits in logs.

Impact Analysis

Attackers can replace or delete content on pages or comments they don't own, reparent existing pages, or modify comments. This could lead to misinformation, data loss, or unauthorized changes to wiki content. The impact is high for data integrity but limited for availability.

Compliance Impact

This vulnerability could violate compliance requirements that mandate data integrity and access controls, such as GDPR's integrity principle or HIPAA's access control safeguards. Unauthorized modifications to sensitive data may lead to non-compliance penalties or data breaches.

Mitigation Strategies

Upgrade YesWiki to version 4.6.7 or later immediately. If upgrading is not possible, restrict write access to the api/comments endpoint via server configuration or firewall rules. Review recent page and comment changes for unauthorized modifications.

Chat Assistant

Ask questions about this CVE
Hi! I’m here to help you understand CVE-2026-104444. Ask me anything about the vulnerability, its impact, or mitigation strategies.
0/70

EPSS Chart