Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessAuthenticate as wiki-go admin
-
ExploitSubmit comment-deletion request with traversal in documentPath
-
ExecutionDeleteComment resolves path outside data/comments
-
Impactos.Remove deletes arbitrary file on host
Vulnerability Assessment
| Weakness |
CWE
OWASP Top 10:2025
A01:2025 - Broken Access Control
ASVS 5.0
V5 - File Handling Path canonicalization, traversal prevention
MITRE ATT&CK
2 techniques across 2 tactics: Discovery, Collection The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up. |
| Exploitation Conditions | Requires an authenticated wiki-go administrator session: the vulnerable DeleteComment handler only executes when userIsAdmin is true, and the attacker must control the documentPath argument sent to the comment-deletion endpoint, supplying traversal sequences (e.g. ../, ..\, or encoded %2e%2e per the added test cases). Affected versions are wiki-go up to and including 1.9.1; 1.9.2 adds path containment. Limiting factors: the admin-privilege requirement (PR:H) is the primary constraint, drastically reducing the viable attacker set; no user interaction is needed (UI:N) and the endpoint is remotely reachable (AV:N), but exploitation is impossible without prior administrative access. |
| Impact | This is a genuine but modest-priority issue. The CVSS 4.0 base vector (AV:N/AC:L/AT:N/PR:H/UI:N, VC:N/VI:L/VA:L) scores 5.1 (Medium), and the signals are internally consistent rather than conflicting: network-reachable (AV:N) and low-complexity (AC:L), but gated behind high privileges (PR:H). The source code confirms why PR:H is correct - DeleteComment only proceeds when userIsAdmin is true, so an attacker must already hold wiki-go administrator rights. A publicly available exploit exists (POC=YES), which raises operational concern, but the CVSS 4.0 vector carries E:P (Proof-of-Concept exploit maturity), not evidence of active campaigns. The CVE is NOT in CISA KEV, so this is: publicly available exploit code exists, with no public evidence of active exploitation. EPSS is not provided in the input, so probabilistic exploitation likelihood cannot be factored in. Impact is bounded - no confidentiality loss (VC:N) and only Low integrity/availability impact (VI:L/VA:L), reflecting that the path-traversal sink is os.Remove (arbitrary file deletion) rather than code execution or data theft. Net assessment: a real, patch-worthy vulnerability but not an emergency, because the admin-privilege prerequisite sharply limits the realistic attacker population. |
| Exploit ScenarioDerived | An authenticated wiki-go administrator (or an attacker who has compromised an admin session) sends a comment-deletion request in which the documentPath parameter contains directory-traversal sequences (e.g. ../../). Because DeleteComment joined documentPath into data/comments without containment, os.Remove operates on a file outside the comments directory, allowing deletion of arbitrary server files. A public exploit/advisory (GHSA-g86r-58wp-4v86) is available, lowering the effort to reproduce. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Oct 21, 2026
Path traversal in the comment-deletion handler of LeoMoon Studios wiki-go through 1.9.1 allows an authenticated wiki administrator to delete files outside the intended comments directory by supplying traversal sequences (such as ../, ..\, or URL-encoded %2e%2e) in the documentPath argument of the comment-deletion request. Because the endpoint is reachable remotely and requires no user interaction, a malicious or compromised admin account can remove arbitrary files writable by the wiki-go process, affecting integrity and availability (assessed CVSS:3.1 AV:N/AC:L/PR:H/UI:N/C:N/I:L/A:L); the file contents are not exposed. Publicly available exploit code exists and the flaw is described in a GitHub security advisory, but there is no indication of active exploitation in the wild. The issue is a genuine but modest-priority one, primarily constrained by the administrative-privilege prerequisite, and is fixed in version 1.9.2.
RemediationAI
Vendor-released patch: upgrade wiki-go to version 1.9.2, which adds path-containment resolution for comment add/get/delete operations and a strict digits-only comment ID validator (commit 224ef2a11facddef6b3a3c1f0a69156d1e574a33; release notes and GHSA-g86r-58wp-4v86). No configuration toggle disables the vulnerable handler, so until patched the primary compensating control is to reduce the admin attack surface: audit and strictly limit who holds wiki administrator rights, enforce strong authentication and MFA on admin accounts, and avoid shared or service admin logins, since exploitation requires an authenticated administrator session (the handler only proceeds when userIsAdmin is true). Additionally, run the wiki-go process under a least-privileged OS account and, where feasible, mount configuration, data and backup directories read-only or outside the process owner's write scope, accepting that this may block legitimate comment storage and other writes; maintain offline, verified backups so any destructive traversal can be recovered without paying an availability cost. Because public exploit code exists, prioritize these controls on any internet-facing deployment and monitor deletion or audit logs for comment-delete requests carrying traversal sequences in the document path.
Affected VersionsENISA
Affected Packages
Source: OSV (Open Source Vulnerabilities)
Affects your stack
Affects 1 package in euvd
Checking this CVE against your own stacks and servers is part of the Basic plan and up.
Technical ContextAI · show details
wiki-go is a Go-based wiki application that stores per-document comments as Markdown files under a comments root (historically the hardcoded data/comments directory). In versions up to 1.9.1, DeleteComment(commentID, documentPath, userIsAdmin) validated only the commentID (via a numeric parse) and then built the target path with filepath.Join("data/comments", documentPath, commentID) before calling os.Remove. Go's filepath.Join cleans the path, collapsing ".." segments, so a documentPath containing traversal sequences escapes the comments root and the deletion lands on an arbitrary file the process can write. The same unvalidated join pattern existed in AddComment and GetComments, which is why the upstream fix refactored all three functions. The patch (commit 224ef2a11facddef6b3a3c1f0a69156d1e574a33, released in v1.9.2) introduces a configurable commentsRoot plus resolveCommentFile/resolveCommentDirectory helpers that enforce containment, replaces the strconv-based comment ID check with a strict digits-only validator that rejects empty strings, and adds regression tests covering "../outside", "..\outside" and "%2e%2e/outside" inputs. This is a classic CWE-22 path traversal whose root cause is missing canonicalization-and-containment checking on a user-controlled path component.
Know when Wiki Go gets its next vulnerability
- Watch products and get an email when something new is published
- Check this CVE against your own stack and servers
- Exploit and PoC references, threat intelligence from 22 sources
No credit card · 7-day full trial
Severity by source
CVSS:4.0/AV:N/AC:L/AT:N/PR:H/UI:N/VC:N/VI:L/VA:L/SC:N/SI:N/SA:N/E:P
DeleteComment is admin-gated so PR:H; remotely reachable low-complexity request gives AV:N/AC:L/UI:N; sink is os.Remove (arbitrary file deletion) so I:L/A:L and C:N.
Primary rating from Vendor (VulDB).
CVSS VectorVendor: VulDB
Lifecycle Timeline
3DescriptionCVE.org
A security vulnerability has been detected in leomoon-studios wiki-go up to 1.9.1. Affected by this issue is the function DeleteComment of the file internal/comments/comments.go of the component Comment Deletion Handler. The manipulation of the argument documentPath leads to path traversal. The attack may be initiated remotely. The exploit has been disclosed publicly and may be used. Upgrading to version 1.9.2 can resolve this issue. The identifier of the patch is 224ef2a11facddef6b3a3c1f0a69156d1e574a33. It is advisable to upgrade the affected component.
Threat Intelligence Overview
How this decision was reached
The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.
What every action level means
SSVC AssessmentENISA
Priority Score
Attack Technique
Path traversal exploits occur when applications use user-controlled input to construct file system paths without proper validation.
Authenticated path traversal in wiki-go 1.9.1 and earlier lets low-privileged users abuse the Files Rename API to move o
Path traversal in Leomoon wiki-go through 1.9.1 allows authenticated users with editor-level privileges to read, overwri
Authenticated server-side request forgery (SSRF) in wiki-go versions up to 1.9.1 allows logged-in users to make the serv
EUVD-2026-107550
GHSA-fh2r-2crp-r75w
NVD
CVE.org
EPSS
VulDB
Exploit-DB