CVE-2026-104451
Deferred Deferred - Pending Action

Cross-Site Request Forgery in YesWiki Leading to Page Revision Restoration

Publication date: 2026-10-02

Last updated on: 2026-10-02

Assigner: VulnCheck

Description
YesWiki before 4.6.7 contains a cross-site request forgery vulnerability in RevisionsHandler that allows attackers to restore old page revisions through GET requests lacking CSRF token validation. Attackers can lure write-capable users into a top-level navigation with the restoreRevisionId parameter, silently overwriting current page content with stale or vandalized revisions.

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-104451
EUVD
EUVD-2026-91462

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-352 The web application does not, or cannot, sufficiently verify whether a request was intentionally provided by the user who sent the request, which could have originated from an unauthorized actor.

Attack-Flow Graph

AI Quick Actions

Instant insights powered by AI
Executive Summary

YesWiki before version 4.6.7 has a CSRF vulnerability in the RevisionsHandler. Attackers can trick users with write permissions into restoring old page revisions via malicious GET requests without proper CSRF token validation. This silently overwrites current page content with stale or vandalized revisions.

Detection Guidance

To detect this vulnerability, check if your YesWiki instance is running a version before 4.6.7. Inspect network traffic for GET requests to the RevisionsHandler endpoint with the restoreRevisionId parameter. Look for suspicious page revisions being restored without user action.

Impact Analysis

An attacker could restore an old revision of a page, removing legitimate edits or reintroducing outdated or malicious content. This affects integrity but does not expose confidential data or disrupt availability directly.

Compliance Impact

This CSRF vulnerability could potentially impact compliance with GDPR and HIPAA by allowing unauthorized content modifications. Under GDPR, integrity of personal data is protected, and unauthorized changes could violate Article 5. Under HIPAA, integrity of protected health information requires safeguards against unauthorized alteration. The vulnerability enables silent content rollbacks that could corrupt records or reintroduce stale data.

Mitigation Strategies

Immediately upgrade YesWiki to version 4.6.7 or later. Ensure all users with write permissions are aware of phishing risks. Monitor page revisions for unauthorized changes and enforce POST requests with CSRF token validation in the RevisionsHandler.

Chat Assistant

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

EPSS Chart