CVE-2026-104440: YesWiki before 4.6.7 contains a blind server-side request forgery vulnerability that allows unauthenticated attackers to make arbitrary server-side
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 21% 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:N/I:L/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. Users should upgrade to version 4.6.7 or later to remediate this vulnerability. Since the vendor advisory or patch links are not provided, verify the patch availability from the official YesWiki sources before upgrading. No other mitigations are indicated.
Description
YesWiki versions before 4.6.7 have a blind server-side request forgery (SSRF) vulnerability in the /api/entries/bazarlist endpoint. This flaw allows unauthenticated attackers to make arbitrary server-side requests by exploiting the idtypeannonce parameter. The vulnerability arises because the isValidURL() function always returns true, enabling attackers to supply internal URLs that the server fetches using curl in loadURLContent(). This can be used to probe internal networks and access internal services or metadata endpoints.