CVE-2026-104439: YesWiki before 4.6.7 contains a user enumeration vulnerability in LostPasswordAction.php that allows unauthenticated attackers to confirm registered
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.3% chance of exploitation in 30 days – higher than 27% 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 fixed version, 4.6.7, is available that addresses this vulnerability. Users should upgrade to YesWiki 4.6.7 or later to remediate this issue. Until upgrading, implementing rate limiting on the password recovery page and ensuring uniform responses regardless of email validity can help mitigate exploitation.
Description
YesWiki versions prior to 4.6.7 have a user enumeration vulnerability in the LostPasswordAction.php component. This flaw allows unauthenticated attackers to confirm whether an email address is registered by observing different responses from the password recovery page. There is no rate limiting on submissions, enabling attackers to automate identification of valid accounts. This can facilitate targeted phishing or password spraying attacks.