GHSA-jp7c-wj6q-3qf2
Gogs vulnerable to arbitrary file deletion via Path Traversal in wiki page update
EPSS Exploitation Probability
EPSS (Exploit Prediction Scoring System) is a daily probability model maintained by FIRST.org. It estimates the likelihood a CVE will be exploited in production environments within the next 30 days, derived from real-world threat intelligence signals.
Blast Radius
gogs.io/gogsReal-time download stats are indexed for npm and PyPI packages. This vulnerability affects Go packages — download data is not available via public APIs for these ecosystems.
Description
Summary
A Path Traversal vulnerability exists in the updateWikiPage function of Gogs. The vulnerability allows an authenticated user with write access to a repository's wiki to delete arbitrary files on the server by manipulating the old_title parameter in the wiki editing form.
Vulnerability Deatils
The vulnerability is located in internal/database/wiki.go. When updating a wiki page, the application accepts an old_title parameter to identify the potential rename operation. This parameter is used directly in path.Join and os.Remove without proper sanitization.
Code snippet from internal/database/wiki.go:
// Line 114
os.Remove(path.Join(localPath, oldTitle+".md"))
If an attacker provides a path traversal sequence (e.g., ../../../../target) as old_title, the os.Remove function will resolve the path relative to the wiki's local directory and delete the target file. The vulnerability is limited to deleting files that end with .md (due to the appended extension), but depending on the filesystem and specific path.Join behavior, or if critical .md files exist (e.g. documentation, other wikis), the impact is significant. Additionally, in some contexts, the extension might be bypassed or ignored.
Impact
- Denial of Service: Deletion of critical configuration files or data (if they match the extension or via other tricks).
- Data Loss: Deletion of other users' wiki pages or documentation.
Remediation
Sanitize the oldTitle parameter using ToWikiPageName (or path.Clean and basename validation) before using it in file operations, similar to how the new title is currently handled.
// Recommended Fix
if oldTitle != "" {
oldTitle = ToWikiPageName(oldTitle)
}
Reproduction Steps
- Log in to Gogs as a user with write access to a repository wiki.
- Intercept the
POSTrequest to/repo/wiki/edit. - Modify the
old_titleparameter to../../../../tmp/target_file. - Submit the request.
- Observe that
/tmp/target_file.mdis deleted from the server.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 🐹Go | gogs.io/gogs | all versions | 0.13.4 |
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for gogs.io/gogs. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.
Fix
Update gogs.io/gogs to 0.13.4 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-jp7c-wj6q-3qf2 is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
How O3 protects you
O3 pinpoints whether GHSA-jp7c-wj6q-3qf2 is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.
Tailored to GHSA-jp7c-wj6q-3qf2. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.
Frequently Asked Questions
Is GHSA-jp7c-wj6q-3qf2 in your dependencies?
O3 detects GHSA-jp7c-wj6q-3qf2 across Go dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.