CVE-2020-5590 — ec-cube
HIGHCVE-2020-5590 is a high-severity (CVSS 8.1) Path Traversal vulnerability in ec-cube/ec-cube. A fix is available for ec-cube/ec-cube — see the affected versions and patch details below.
EC-CUBE Directory traversal vulnerability
EPSS Exploitation Probability
Probability of exploitation in the next 30 days, from FIRST.org EPSS.
How urgent is this, really
Where this sits among everything scored
Real-World Exposure
ec-cube/ec-cube🐘ec-cube/ec-cubeReal-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
| 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.4composer require ec-cube/ec-cube:^4.0.4 |
Affected Products
ec-cubeec-cubeDetection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for ec-cube/ec-cube, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
A fix is available for CVE-2020-5590; check the affected-versions list above or the advisory for the patched release of ec-cube/ec-cube, then make sure no transitive dependency still pins the vulnerable range.
Workarounds
Resolve every user-supplied path to its canonical form and reject anything that escapes the intended directory, and run the component under an account that has no read or write access outside the directory it legitimately serves.
Frequently Asked Questions
Is CVE-2020-5590 in your dependencies?
Find it across Packagist, including transitive dependencies.