CVE-2026-104438: YesWiki before 4.6.7 contains a missing authorization vulnerability in the listpagestag and includepages actions of the tags tool, which enumerate
Affects yeswikiSource GCVE Database
Not known to be exploited · CVSS 5.3 Medium : upgrade to 4.6.7 when convenient.
Data as of 16 Nov 2026, 20:25 UTC
- EPSS
- 0.2% chance of exploitation in 30 days – higher than 22% 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:N/S:U/C:L/I:N/A:NExploitation evidence
Disclosed: evidence found.
CVE published 2 Oct 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by 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
| Product | Affected | Fixed in |
|---|---|---|
GitHubyeswiki/yeswikipkg:github/yeswiki/yeswikiOther threats | Affected
| Fixed in
|
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 missing authorization issue. Users should upgrade to version 4.6.7 or later to remediate this vulnerability. Until patched, restrict access to the affected actions or monitor for suspicious use if possible.
Description
YesWiki versions prior to 4.6.7 have a missing authorization vulnerability in the tags tool's listpagestag and includepages actions. This flaw allows unauthenticated or unprivileged attackers to enumerate page names and titles of pages protected by access control lists (ACLs) without proper read permission checks. The vulnerability can lead to unauthorized disclosure of page metadata but does not impact page content integrity or availability.