How severe is CVE-2020-10806?

CVE-2020-10806 has a CVSS score of 9.8/10, rated CRITICAL. Immediate patching is strongly recommended.

Which packages are affected by CVE-2020-10806?

CVE-2020-10806 affects the following packages: ezsystems/ezpublish-kernel (Packagist), ezsystems/ezpublish-legacy (Packagist), ezsystems/ezpublish-kernel (Packagist), ezsystems/ezpublish-kernel (Packagist), ezsystems/ezpublish-legacy (Packagist), ezsystems/ezpublish-legacy (Packagist). Ecosystems affected: Packagist.

How do I fix CVE-2020-10806?

Update ezsystems/ezpublish-kernel to 5.4.14.1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2020-10806 is resolved across your whole dependency graph.

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

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for ezsystems/ezpublish-kernel, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

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

Treat uploaded files as untrusted until proven otherwise: validate the actual content type rather than the supplied extension, store uploads outside the web root on a volume mounted without execute permission, and rename them to server-generated identifiers so an attacker cannot choose the path a request will later resolve.

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

No public exploit code has been indexed for CVE-2020-10806 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 is the EPSS score for CVE-2020-10806?

CVE-2020-10806 has an EPSS (Exploit Prediction Scoring System) score of 2.3%, placing it in the 84th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

What type of vulnerability is CVE-2020-10806?

CVE-2020-10806 is classified as Unrestricted File Upload (CWE-434). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

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

CVE-2020-10806 was published on March 22, 2020 and was last updated on October 24, 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

Not in CISA KEV

CRITICAL severity

CVE-2020-10806 — ezpublish-kernel

CRITICAL

CVE-2020-10806 is a critical-severity (CVSS 9.8) Unrestricted File Upload vulnerability in ezsystems/ezpublish-kernel. A fix is available for ezsystems/ezpublish-kernel — see the affected versions and patch details below.

eZ Publish Kernel and Legacy Unrestricted Upload of File with Dangerous Type

Also known asGHSA-54p5-gxq6-j98g

Published

Mar 22, 2020

Updated

Oct 24, 2026

Affected

6 pkgs

Patched

6 / 6

Exploits

None indexed

Exploitation data as of Nov 4, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

EPSS Exploitation Probability

via FIRST.org ↗

2.3%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs84th percentile — riskier than 84% of all scored CVEsHighest risk

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

6 pkgs affected

🐘ezsystems/ezpublish-kernel🐘ezsystems/ezpublish-legacy🐘ezsystems/ezpublish-kernel🐘ezsystems/ezpublish-kernel🐘ezsystems/ezpublish-legacy🐘ezsystems/ezpublish-legacy

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

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.

Affected Packages

6 total 6 fixed

Ecosystem	Package	Vulnerable range	Fix
🐘Packagist	`ezsystems/ezpublish-kernel`	all versions	5.4.14.1`composer require ezsystems/ezpublish-kernel:^5.4.14.1`
🐘Packagist	`ezsystems/ezpublish-legacy`	all versions	5.4.14.1`composer require ezsystems/ezpublish-legacy:^5.4.14.1`
🐘Packagist	`ezsystems/ezpublish-kernel`	≥ 6.0&&< 6.13.6.2	6.13.6.2`composer require ezsystems/ezpublish-kernel:^6.13.6.2`
🐘Packagist	`ezsystems/ezpublish-kernel`	≥ 7.0&&< 7.5.6.2	7.5.6.2`composer require ezsystems/ezpublish-kernel:^7.5.6.2`
🐘Packagist	`ezsystems/ezpublish-legacy`	≥ 2017&&< 2017.12.7.2	2017.12.7.2`composer require ezsystems/ezpublish-legacy:^2017.12.7.2`
🐘Packagist	`ezsystems/ezpublish-legacy`	≥ 2019&&< 2019.03.4.2	2019.03.4.2`composer require ezsystems/ezpublish-legacy:^2019.03.4.2`

Affected Products

2 products · 6 configurations

Application

ez publish-kernelez

≥ 7.0.0 && < 7.5.6.2

range

Application

ez publish-legacyez

≥ 2019.0 && < 2019.03.4.2

range

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for ezsystems/ezpublish-kernel, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update ezsystems/ezpublish-kernel to 5.4.14.1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2020-10806 is resolved across your whole dependency graph.
Workarounds
Treat uploaded files as untrusted until proven otherwise: validate the actual content type rather than the supplied extension, store uploads outside the web root on a volume mounted without execute permission, and rename them to server-generated identifiers so an attacker cannot choose the path a request will later resolve.

Frequently Asked Questions

O3 Security · Impact-Aware SCA

Is CVE-2020-10806 in your dependencies?

Find it across Packagist, including transitive dependencies.

Scan my dependencies How O3 SCA works

CVSS Score

9.8/10CVSS v3 base

Vector breakdown

Attack Vector

Network

Attack Complexity

Low

Privileges Required

None

User Interaction

None

Scope

Unchanged

Confidentiality

High

Integrity

High

Availability

High

Raw vector

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

CWE Classification

CWE-434Unrestricted File Upload

Weaponization

No Nuclei template, Metasploit module or public proof-of-concept found.

Timeline

Disclosed

Mar 22, 2020

Last updated

Oct 24, 2026

Identifiers

CVE-2020-10806

GHSA-54p5-gxq6-j98g

References

Advisoryezplatform.com · ezsa 2020 001 remote code execution in file uploads Advisorynvd.nist.gov · CVE 2020 10806

Related vulnerabilities

This CVE is critical severity; 2 of 8 other CVEs affecting ezsystems/ezpublish-kernel are rated as high or higher (top: critical).

GHSA-3vwr-jj4f-h98xGHSA-64vj-933f-6pm3GHSA-9wwx-c723-vm8xGHSA-946c-f9w6-2c25CVE-2022-48366CVE-2022-48367CVE-2022-48365GHSA-99r3-xmmq-7q7g

Provenance

Sources

OSV.devNVDFIRST.org (EPSS)

Last verifiedOct 24, 2026

CVE-2020-10806 — ezpublish-kernel

EPSS Exploitation Probability

How urgent is this, really

Where this sits among everything scored

Real-World Exposure

Description

Affected Packages

Affected Products

Detection & mitigation playbook

Detect

Fix

Workarounds

Frequently Asked Questions

Is CVE-2020-10806 in your dependencies?