Skip to main content
VulnerabilityPublished

CVE-2026-104451: YesWiki before 4.6.7 contains a cross-site request forgery vulnerability in RevisionsHandler that allows attackers to restore old page revisions

Affects yeswikiSource GCVE Database

0
Compare

Not known to be exploited · CVSS 4.3 Medium : upgrade to 4.6.7 when convenient.

Data as of 16 Nov 2026, 20:25 UTC

CVSS 3.1 base score
4.3Medium
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.1% chance of exploitation in 30 days – higher than 2% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 4.6.7
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:L/A:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 2 Oct 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 16 Nov 2026.

What to do

Upgrade yeswiki/yeswiki to 4.6.7.

Affected software

ProductAffectedFixed in
GitHubyeswiki/yeswikipkg:github/yeswiki/yeswikiOther threatsAffected
  • <4.6.7
Fixed in
  • 4.6.7

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

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.

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.

References

Community reviews

Loading reviews…