CVE-2026-114376: leomoon-studios wiki-go advisory

Advisory generated from the CVE record, CISA, Exploit Observer and VEDAS: what it is, whether it is exploited, who is affected, and how to fix and detect it.

What it is

A weakness has been identified in leomoon-studios wiki-go up to 1.9.1. Affected by this vulnerability is the function SaveHandler/SourceHandler of the file internal/handlers/editor.go of the component API. Executing a manipulation can lead to path traversal. The attack can be launched remotely. The exploit has been made available to the public and could be used for attacks. Upgrading to version 1.9.2 addresses this issue. This patch is called 94f7e73ef8df7c58091d72d77a5e26e9fdad98b8. Upgrading the affected component is advised.

Description quoted from the CVE record (assigned by VulDB, published 2026-10-21).

Weakness: Path Traversal

How it can be exploited

Exploitable over the network with low attack complexity with no special attack requirements needing low privileges and no user interaction. Impact: confidentiality low, integrity low, availability low. CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N/E:P

CISA assessment (SSVC): CISA assesses that a public proof of concept exists. Automatable: no. Technical impact: partial.

Public exploit evidence (Exploit Observer)

Exploit Observer found 3 code repositories naming this CVE.

Code repositories that name a CVE are often scanners, copies or fakes, and some are malware. Read the code before running anything.

See all 5 references on Exploit Observer

Live scores

EPSS: 0.003
low predicted chance of attack
VEDAS: 0.987
strong exploit evidence
On CISA KEV: Not listed
Detection rule: Suricata

Who is affected

Product	Affected	Not affected
leomoon-studios wiki-go	version 1.9.0 version 1.9.1	1.9.2 is not affected

Version ranges exactly as the CVE record states them. “Before X” means X is the first fixed version.

How to fix it

Vendor guidance:

How to detect it

Suricata rules (network detection)

1 rule that alert on traffic matching this exploit: VEDAS CVE-2026-114376 wiki-go Editor API /api/source Path Traversal Arbitrary File Read. Add them to your Suricata rule set and reload.

Show the rules

suricata

alert http $EXTERNAL_NET any -> $HTTP_SERVERS $HTTP_PORTS (msg:"VEDAS CVE-2026-114376 wiki-go Editor API /api/source Path Traversal Arbitrary File Read"; flow:established,to_server; http.uri.raw; content:"/api/source/"; fast_pattern; pcre:"/\/api\/source\/.{0,300}(\.\.(\/|\\)|%2e|%252e)/i"; classtype:web-application-attack; reference:cve,CVE-2026-114376; reference:url,https://www.exploit.observer/?keyword=CVE-2026-114376&match=exact; reference:url,https://subdomain.center/?engine=ammonites&keyword=wiki-go&match=exact; sid:1082600; rev:1;)

CVE-2026-114376.rules on GitHub

References

Vendor advisories and patches

Other databases

Where this comes from

This advisory is generated automatically by VEDAS from: CVE.org record, cve-scores (EPSS and VEDAS), Exploit Observer, vedas-signatures. Text in quotes is reproduced from the source; everything else is a fixed template filled with source fields. Nothing here is written by a language model. Check the vendor advisory before acting, and read how VEDAS and Exploit Observer work, and their limits.