# CVE-2018-20064: Path traversal in n/a

> Remote attackers can write arbitrary files via directory traversal in doorGets, potentially leading to code execution.

- **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:** No
- **Published:** 11 Dec 2018
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-778m-r9w8-v3q7

## What is CVE-2018-20064?

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

### Official description

doorGets 7.0 allows remote attackers to write to arbitrary files via directory traversal, as demonstrated by a dg-user/?controller=theme&action=edit&name=doorgets&file=../../1.txt%00 URI with content in the theme_content_nofi parameter.

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

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

It affects 1 product.


Products: Doorgets Doorgets.

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

No fix has been published for CVE-2018-20064 yet. Limit exposure of the affected software until one is available.

## Is CVE-2018-20064 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2018-11126](https://insights.sbomify.com/CVE-2018-11126/): Cross-site request forgery in n/a (high 8.8)

## Fix prompt for AI coding agents

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

What it is: CVE-2018-20064 is a high-severity path traversal vulnerability in n/a, published on 11 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-20064 in the wild and no public exploit code.

Affected product: n/a. No package-level version data is available, so check the vendor advisory linked from the reference page.

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-20064/ (Markdown: https://insights.sbomify.com/CVE-2018-20064/index.md)
```

## Sources

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

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