YesWiki before 4.6.7 contains a cross-site request forgery vulnerability in RevisionsHandler that allows attackers to restore old page revisions… (CVE-2026-104451)
YesWiki versions prior to 4.6.7 have a cross-site request forgery (CSRF) vulnerability in the RevisionsHandler component. This flaw allows attackers to trick authorized users into restoring old page revisions via specially crafted GET requests that do not require a CSRF token. Exploitation can result in silent overwriting of current page content with outdated or vandalized revisions without user awareness.
AI Analysis
Technical Summary
The vulnerability in YesWiki before version 4.6.7 is a CSRF issue in the RevisionsHandler. It arises because GET requests that trigger restoration of old page revisions lack proper CSRF token validation. An attacker can exploit this by inducing a write-capable user to visit a URL containing the restoreRevisionId parameter, causing the user's browser to send a request that restores a previous revision of a page. This leads to unauthorized modification of page content without explicit user consent.
Potential Impact
Successful exploitation results in integrity loss of page content by restoring stale or vandalized revisions without the user's knowledge. There is no impact on confidentiality or availability. The vulnerability requires user interaction (UI:R) but no privileges (PR:N) and can be exploited remotely (AV:N).
Mitigation Recommendations
A fix is available in YesWiki version 4.6.7 that addresses this CSRF vulnerability by enforcing proper token validation on revision restoration requests. Users should upgrade to version 4.6.7 or later to remediate this issue. No other mitigation guidance is provided.
YesWiki before 4.6.7 contains a cross-site request forgery vulnerability in RevisionsHandler that allows attackers to restore old page revisions… (CVE-2026-104451)
Description
YesWiki versions prior to 4.6.7 have a cross-site request forgery (CSRF) vulnerability in the RevisionsHandler component. This flaw allows attackers to trick authorized users into restoring old page revisions via specially crafted GET requests that do not require a CSRF token. Exploitation can result in silent overwriting of current page content with outdated or vandalized revisions without user awareness.
CVSS v3.1
Score 4.3medium
Affected software
Run on your own infrastructure? Check whether these packages are installed with threat-finder — our free open-source scanner.
Weaknesses
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
The vulnerability in YesWiki before version 4.6.7 is a CSRF issue in the RevisionsHandler. It arises because GET requests that trigger restoration of old page revisions lack proper CSRF token validation. An attacker can exploit this by inducing a write-capable user to visit a URL containing the restoreRevisionId parameter, causing the user's browser to send a request that restores a previous revision of a page. This leads to unauthorized modification of page content without explicit user consent.
Potential Impact
Successful exploitation results in integrity loss of page content by restoring stale or vandalized revisions without the user's knowledge. There is no impact on confidentiality or availability. The vulnerability requires user interaction (UI:R) but no privileges (PR:N) and can be exploited remotely (AV:N).
Mitigation Recommendations
A fix is available in YesWiki version 4.6.7 that addresses this CSRF vulnerability by enforcing proper token validation on revision restoration requests. Users should upgrade to version 4.6.7 or later to remediate this issue. No other mitigation guidance is provided.
Technical Details
- Gcve Source
- db.gcve.eu
- Osv Id
- GHSA-q9vm-p57f-8mmp
- Osv Schema Version
- 1.4.0
- Aliases
- ["CVE-2026-104451"]
- Database Specific Severity
- MODERATE
- Cvss Version
- 3.1
Threat ID: 6abfee8aa43b0b3b89e54bf4
Added to database: 10/02/2026, 17:48:58 UTC
Last enriched: 10/02/2026, 17:58:21 UTC
Last updated: 10/02/2026, 21:26:15 UTC
Views: 3
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.