# CVE-2020-7998: File upload in n/a

> Attackers can upload arbitrary files via the exposed FTP or Web UI due to missing default authentication, potentially leading to code execution or data modification.

- **Severity:** High 8.8 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 28 Jan 2020
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-rxwr-r7r7-crrp

## What is CVE-2020-7998?

CVE-2020-7998 is a high-severity vulnerability in n/a, published on 28 Jan 2020. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

An arbitrary file upload vulnerability has been discovered in the Super File Explorer app 1.0.1 for iOS. The vulnerability is located in the developer path that is accessible and hidden next to the root path. By default, there is no password set for the FTP or Web UI service.

Weakness: CWE-434 (Unrestricted Upload of File with Dangerous Type)

## Which versions are affected by CVE-2020-7998?

It affects 1 product.


Products: Super File Explorer Project Super File Explorer.

## How do I fix CVE-2020-7998?

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

## Is CVE-2020-7998 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2020-7998 and fix it if it is affected.

What it is: CVE-2020-7998 is a high-severity vulnerability in n/a, published on 28 Jan 2020. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2020-7998 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-2020-7998/ (Markdown: https://insights.sbomify.com/CVE-2020-7998/index.md)
```

## Sources

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

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