CVE-2020-10806 json
eZ Publish Kernel and Legacy Unrestricted Upload of File with Dangerous Type
published 6y ago modified 4mo ago also GHSA-54p5-gxq6-j98g , EUVD-2022-2496
- cvss
- 9.8
- version 3.1, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 2.3%
- EPSS 2.3% chance of exploitation in 30 days, percentile 83%
- public exploits
- 0
- none known
Summary
eZ Publish Kernel before 5.4.14.1, 6.x before 6.13.6.2, and 7.x before 7.5.6.2 and eZ Publish Legacy before 5.4.14.1, 2017 before 2017.12.7.2, and 2019 before 2019.03.4.2 allow remote attackers to execute arbitrary code by uploading PHP code, unless the vhost configuration permits only app.php execution.
Patch / fix
- packagist ezsystems/ezpublish-kernel 5.4.14.1, 6.13.6.2, 7.5.6.2
- packagist ezsystems/ezpublish-legacy 5.4.14.1, 2017.12.7.2, 2019.03.4.2
- ez ez_publish-kernel 5.4.14.1, 6.13.6.2, 7.5.6.2
- ez ez_publish-legacy 5.4.14.1, 2017.12.7.2, 2019.03.4.2
Is CVE-2020-10806 in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerExploit prediction
2.32% chance of exploitation in the next 30 days, higher than 83% of all scored CVEs (FIRST EPSS, 2026-11-09).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 3.1 | 9.8 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H |
| NVD | 2.0 | 7.5 | AV:N/AC:L/Au:N/C:P/I:P/A:P |
| GitHub | 3.1 | 9.8 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H |
Affected packages
| ecosystem | package | affected | fixed in |
|---|---|---|---|
| packagist | ezsystems/ezpublish-kernel | <5.4.14.1 >=6.0, <6.13.6.2 >=7.0, <7.5.6.2 |
5.4.14.1 6.13.6.2 7.5.6.2 |
| packagist | ezsystems/ezpublish-legacy | <5.4.14.1 >=2017, <2017.12.7.2 >=2019, <2019.03.4.2 |
5.4.14.1 2017.12.7.2 2019.03.4.2 |
Classification
- Weakness
-
- CWE-434 Unrestricted Upload of File with Dangerous Type
References
Sources
- CVE List CVE-2020-10806
- GitHub Advisory GHSA-54p5-gxq6-j98g
- NVD CVE-2020-10806
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.