How severe is CVE-2020-5590?

CVE-2020-5590 has a CVSS score of 8.1/10, rated HIGH. Immediate patching is strongly recommended.

Which packages are affected by CVE-2020-5590?

CVE-2020-5590 affects the following packages: ec-cube/ec-cube (Packagist), ec-cube/ec-cube (Packagist). Ecosystems affected: Packagist.

How do I fix CVE-2020-5590?

No patched version of ec-cube/ec-cube has shipped for CVE-2020-5590 yet. Where your build allows, override or pin the dependency away from the vulnerable range, and apply any maintainer-recommended mitigation.

How do I detect CVE-2020-5590 in my Packagist dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for ec-cube/ec-cube. 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.

How do I mitigate CVE-2020-5590 if there is no patch (or I can't update yet)?

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 does O3 Security protect against CVE-2020-5590?

O3 pinpoints whether CVE-2020-5590 is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Is CVE-2020-5590 actively exploited in the wild?

No public exploit code has been indexed for CVE-2020-5590 yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

What type of vulnerability is CVE-2020-5590?

CVE-2020-5590 is classified as Path Traversal (CWE-22). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation. This is a high-impact weakness class that often enables remote code execution or data exposure.

When was CVE-2020-5590 published, and has it been updated?

CVE-2020-5590 was published on June 19, 2020 and was last updated on July 8, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

🐘 Packagist

CVE-2020-5590

HIGH

CVE-2020-5590 is a high-severity (CVSS 8.1) Path Traversal vulnerability in ec-cube/ec-cube. O3 Security confirms whether CVE-2020-5590 is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.

EC-CUBE Directory traversal vulnerability

Also known asGHSA-hx79-x87c-hgm3

Published

Jun 19, 2020

Updated

Jul 8, 2026

Affected

2 pkgs

Patched

1 / 2

Exploits

None indexed

Blast Radius

2 pkgs affected

🐘ec-cube/ec-cube🐘ec-cube/ec-cube

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects Packagist packages — download data is not available via public APIs for these ecosystems.

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.

Affected Packages

2 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
🐘Packagist	`ec-cube/ec-cube`	≥ 3.0.0	No fix
🐘Packagist	`ec-cube/ec-cube`	≥ 4.0.0&&< 4.0.4	4.0.4

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for ec-cube/ec-cube. 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
No patched version of ec-cube/ec-cube has shipped for CVE-2020-5590 yet. Where your build allows, override or pin the dependency away from the vulnerable range, and apply any maintainer-recommended mitigation.
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 CVE-2020-5590 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 CVE-2020-5590. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

O3 Security · Impact-Aware SCA

Is CVE-2020-5590 in your dependencies?

O3 detects CVE-2020-5590 across Packagist dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.

Scan my dependencies How O3 SCA works