# CVE-2018-20303: Gogs Directory Traversal

> An attacker can exploit a directory traversal flaw in Gogs to create arbitrary files on the server via the file-upload functionality.

- **Severity:** High 7.5 (`CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 20 Dec 2018
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-9hxg-w7qf-hh93

## What is CVE-2018-20303?

CVE-2018-20303 is a high-severity path traversal vulnerability in n/a, published on 20 Dec 2018. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

In pkg/tool/path.go in Gogs before 0.11.82.1218, a directory traversal in the file-upload functionality can allow an attacker to create a file under data/sessions on the server, a similar issue to CVE-2018-18925.

Weakness: CWE-22 (Improper Limitation of a Pathname to a Restricted Directory)

## Which versions are affected by CVE-2018-20303?

2 open source packages ship an affected version, including gogs.io/gogs. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `gogs.io/gogs` | Go | All versions | 0.11.80-0.20181218063808-ff93d9dbda5c |
| `gogs.io/gogs` | Go | All versions | 0.11.80-0.20181218063808-ff93d9dbda5c |

Products: Gogs Gogs.

## How do I fix CVE-2018-20303?

Upgrade gogs.io/gogs to 0.11.80-0.20181218063808-ff93d9dbda5c or later.

## Is CVE-2018-20303 being exploited?

There is no known exploitation of CVE-2018-20303 in the wild and no public exploit code.

## Other vulnerabilities in n/a

- [CVE-2025-8110](https://insights.sbomify.com/CVE-2025-8110/): Gogs Path Traversal (high 8.7, exploited in the wild)
- [CVE-2024-56731](https://insights.sbomify.com/CVE-2024-56731/): Gogs deletion of internal files allows remote command execution (critical 10.0)
- [CVE-2022-1884](https://insights.sbomify.com/CVE-2022-1884/): Remote Command Execution in gogs/gogs (critical 10.0)
- [CVE-2022-1986](https://insights.sbomify.com/CVE-2022-1986/): OS Command Injection in gogs/gogs (critical 10.0)
- [CVE-2022-1992](https://insights.sbomify.com/CVE-2022-1992/): Path Traversal in gogs/gogs (critical 10.0)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2018-20303 and fix it if it is affected.

What it is: CVE-2018-20303 is a high-severity path traversal vulnerability in n/a, published on 20 Dec 2018. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2018-20303 in the wild and no public exploit code.

Affected packages and fixed versions:
- gogs.io/gogs (Go): affected all versions; fixed in 0.11.80-0.20181218063808-ff93d9dbda5c
- gogs.io/gogs (Go): affected all versions; fixed in 0.11.80-0.20181218063808-ff93d9dbda5c

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2018-20303/ (Markdown: https://insights.sbomify.com/CVE-2018-20303/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2018-20303
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2018-20303
- OSV: https://osv.dev/vulnerability/CVE-2018-20303

---
From sbomify Insights: https://insights.sbomify.com/CVE-2018-20303/
Summaries are generated and may contain mistakes; the official description above is the record.