# CVE-2020-5590: EC-CUBE Directory traversal vulnerability

> Authenticated attackers can delete arbitrary files and directories on EC-CUBE servers via directory traversal.

- **Severity:** High 8.1 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/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:** Yes
- **Published:** 19 Jun 2020
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-hx79-x87c-hgm3

## What is CVE-2020-5590?

CVE-2020-5590 is a high-severity path traversal vulnerability in EC-CUBE, published on 19 Jun 2020. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Directory traversal vulnerability in EC-CUBE 3.0.0 to 3.0.18 and 4.0.0 to 4.0.3 allows remote authenticated attackers to delete arbitrary files and/or directories on the server via unspecified vectors.

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

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

4 open source packages ship an affected version, including ec-cube/ec-cube. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `ec-cube/ec-cube` | Packagist | From 3.0.0 to 3.0.18 | None |
| `ec-cube/ec-cube` | Packagist | From 3.0.0 to 3.0.18 | None |
| `ec-cube/ec-cube` | Packagist | From 4.0.0 | 4.0.4 |
| `ec-cube/ec-cube` | Packagist | From 4.0.0 | 4.0.4 |

Products: Ec-Cube Ec-Cube.

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

Upgrade ec-cube/ec-cube to 4.0.4 or later.

## Is CVE-2020-5590 being exploited?

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

## Other vulnerabilities in EC-CUBE

- [CVE-2021-20778](https://insights.sbomify.com/CVE-2021-20778/): Missing authorization in EC-CUBE (high 7.5)
- [CVE-2020-5680](https://insights.sbomify.com/CVE-2020-5680/): EC-CUBE Improper input validation vulnerability (high 7.5)
- [CVE-2008-4991](https://insights.sbomify.com/CVE-2008-4991/): SQL injection in n/a (high 7.5)
- [CVE-2008-4534](https://insights.sbomify.com/CVE-2008-4534/): SQL injection in n/a (high 7.5)
- [CVE-2023-46845](https://insights.sbomify.com/CVE-2023-46845/): Code injection in EC-CUBE 3 series (high 7.2)

## Fix prompt for AI coding agents

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

What it is: CVE-2020-5590 is a high-severity path traversal vulnerability in EC-CUBE, published on 19 Jun 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-5590 in the wild and no public exploit code.

Affected packages and fixed versions:
- ec-cube/ec-cube (Packagist): affected from 3.0.0 up to 3.0.18; no fix listed
- ec-cube/ec-cube (Packagist): affected from 3.0.0 up to 3.0.18; no fix listed
- ec-cube/ec-cube (Packagist): affected from 4.0.0; fixed in 4.0.4
- ec-cube/ec-cube (Packagist): affected from 4.0.0; fixed in 4.0.4

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

## Sources

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

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