Skip to main content
CVE-2026-116827VulnerabilityPublished

YesWiki before 4.7.0 contains a server-side request forgery vulnerability in the Bazar CSV import copyUrlToLocalFile()

Affects yeswikiSource GCVE Database

0
Authoritative record:CVE-2026-116827· High 8.2

Not known to be exploited · CVSS 8.2 High : upgrade to 4.7.0 soon.

Data as of 27 Oct 2026, 01:59 UTC

CVSS 4.0 base score
8.2High
How severe the flaw is on the 0–10 CVSS scale.
Patch
Available – fixed in 4.7.0
CVSS:4.0/AV:N/AC:L/AT:N/PR:H/UI:N/VC:H/VI:N/VA:N/SC:H/SI:N/SA:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 26 Oct 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: 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 26 Oct 2026.

What to do

Upgrade yeswiki/yeswiki to 4.7.0.

Affected software

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

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.7.0 and later. Users should upgrade to version 4.7.0 or newer to remediate this vulnerability. No other mitigation or temporary workaround is indicated in the provided data.

Description

YesWiki versions prior to 4.7.0 have a server-side request forgery (SSRF) vulnerability in the Bazar CSV import function copyUrlToLocalFile(). Authenticated administrators can exploit this by supplying crafted URLs in CSV or image fields, allowing arbitrary outbound requests. The vulnerability enables bypassing extension checks via query-string suffixes or redirects, potentially exposing cloud metadata credentials, internal services, or local files. Responses are stored in a web-accessible directory, increasing exposure risk.

References

Community reviews

Loading reviews…