Skip to main content
VulnerabilityPublished

CVE-2026-104463: YesWiki before 4.6.7 contains a server-side request forgery vulnerability that allows unauthenticated attackers to trigger server requests by

Affects yeswikiSource GCVE Database

0
Compare

Not known to be exploited · CVSS 7.0 High : upgrade to 4.6.7 soon.

Data as of 16 Nov 2026, 20:25 UTC

CVSS 3.1 base score
7.0High
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.2% chance of exploitation in 30 days – higher than 17% 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:H/PR:N/UI:N/S:U/C:H/I:L/A:L

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

Since the vulnerability affects versions before 4.6.7, upgrading to version 4.6.7 or later is likely the intended remediation. Until official guidance is available, restrict access to the affected public forms actor inbox route and monitor for suspicious signed Follow activities.

Description

YesWiki versions prior to 4.6.7 have a server-side request forgery (SSRF) vulnerability. This flaw allows unauthenticated attackers to send signed Follow activities to a public actor inbox route, causing the server to make unauthorized internal requests. Attackers can use their own keyId to sign these requests while specifying internal actor URLs, potentially accessing internal hosts or cloud metadata services. The vulnerability has a high severity rating with a CVSS score of 7.

References

Community reviews

Loading reviews…