Is ezsystems/ezpublish-legacy vulnerable?

Composer ezsystems/ezpublish-legacy has 18 known advisories in the phpwarden feed. Feed 2026.10.29.1, updated 2026-10-28.

18advisories
1critical
0on CISA KEV
1no fix recorded
CVETitleSeverityCVSSAffectedFixed in
CVE-2020-10806eZ Publish Kernel and Legacy Unrestricted Upload of File with Dangerous Typecritical9.8<5.4.14.1 or >=2017 and <2017.12.7.2 or >=2019 and <2019.03.4.25.4.14.1, 2017.12.7.2, 2019.03.4.2
CVE-2017-1000431eZ Publish Cross-site Scripting (XSS) vulnerabilitymedium6.1>=5.4.0 and <5.4.10 or >=5.3.0 and <5.3.12.15.4.10, 5.3.12.1
CVE-2026-38739ezsystems/ezpublish-legacy has a SQL injection in dfscleanuphigh7.1=2019.03–
2017-09-11-1EZSA-2017-006 Information disclosure in backend content tree menuunknown0.0>=2011.0.0 and <2017.8.1.1 or >=5.4.0 and <5.4.10.1 or >=5.3.0 and <5.3.12.22017.8.1.1, 5.4.10.1, 5.3.12.2
2018-02-26-1EZSA-2018-001 Several vulnerabilities in Forgot password, Information collector, XML text, and Matrix field type featuresunknown0.0>=2011.0.0 and <2017.12.2.1 or >=5.4.0 and <5.4.11.3 or >=5.3.0 and <5.3.12.32017.12.2.1, 5.4.11.3, 5.3.12.3
2018-10-31-1EZSA-2018-005 Passwordless login for LDAP usersunknown0.0>=2018.9.0 and <2018.9.1.1 or >=2018.6.0 and <2018.6.1.2 or >=2011.0.0 and <2017.12.4.1 or >=5.4.0 and <5.4.12.1 or >=5.3.0 and <5.3.12.42018.9.1.1, 2018.6.1.2, 2017.12.4.1, 5.4.12.1
2018-11-01-1EZSA-2018-006 XSS vulnerability in 'disabled module' error templateunknown0.0>=2018.9.0 and <2018.9.1.2 or >=2018.6.0 and <2018.6.1.3 or >=2011.0.0 and <2017.12.4.2 or >=5.4.0 and <5.4.12.2 or >=5.3.0 and <5.3.12.52018.9.1.2, 2018.6.1.3, 2017.12.4.2, 5.4.12.2
2018-11-21-1EZSA-2018-009 Do not interpret PHP/PHAR uploadsunknown0.0>=2018.9.0 and <2018.9.1.3 or >=2018.6.0 and <2018.6.1.4 or >=2011.0.0 and <2017.12.4.3 or >=5.4.0 and <5.4.12.3 or >=5.3.0 and <5.3.12.62018.9.1.3, 2018.6.1.4, 2017.12.4.3, 5.4.12.3
2020-03-03-1EZSA-2020-001 Remote code execution in file uploadsunknown0.0>=2019.3.0 and <2019.3.4.2 or >=2017.12.0 and <2017.12.7.2 or >=5.4.0 and <5.4.14.12019.3.4.2, 2017.12.7.2, 5.4.14.1
2020-10-05-1IBEXA-SA-2020-006 Object Injection in legacy shop moduleunknown0.0>=2019.3.0 and <2019.3.5.1 or >=2017.12.0 and <2017.12.7.3 or >=5.4.0 and <5.4.14.22019.3.5.1, 2017.12.7.3, 5.4.14.2
GHSA-2vh3-cj9j-mcj5eZ Publish Legacy Cross-site Scripting (XSS) in 'disabled module' error templatemedium0.0>=2018.9.0 and <2018.9.1.2 or >=2018.6.0 and <2018.6.1.3 or >=2011.0.0 and <2017.12.4.2 or >=5.4.0 and <5.4.12.2 or >=5.3.0 and <5.3.12.52018.9.1.2, 2018.6.1.3, 2017.12.4.2, 5.4.12.2
GHSA-39j2-4p9j-5w4jEz Platform Object Injection in legacy shop modulemedium0.0>=2019.3.0 and <2019.3.5.1 or >=2017.12.0 and <2017.12.7.3 or >=5.4.0 and <5.4.14.22019.3.5.1, 2017.12.7.3, 5.4.14.2
GHSA-82rv-45pc-v28weZ Publish Legacy Patch EZSA-2018-001 for Several vulnerabilitieshigh0.0>=2011.0.0 and <2017.12.2.1 or >=5.4.0 and <5.4.11.3 or >=5.3.0 and <5.3.12.32017.12.2.1, 5.4.11.3, 5.3.12.3
GHSA-9895-26wr-4fgvEZsystems Remote code execution in file uploadshigh0.0>=2019.3.0 and <2019.3.4.2 or >=2017.12.0 and <2017.12.7.2 or >=5.4.0 and <5.4.14.12019.3.4.2, 2017.12.7.2, 5.4.14.1
GHSA-cc2j-92jq-wgjgeZ Publish Information disclosure in backend content tree menuhigh0.0>=2011.0.0 and <2017.8.1.1 or >=5.4.0 and <5.4.10.1 or >=5.3.0 and <5.3.12.22017.8.1.1, 5.4.10.1, 5.3.12.2
GHSA-jpwx-ffjq-wr4wContent object state fetch functions open to SQL injectionhigh0.0>=2018.06.0 and <2019.03.6.1 or <2017.12.7.42019.03.6.1, 2017.12.7.4
GHSA-p9mp-vq4v-v5m5eZ Publish Legacy Passwordless login for LDAP usershigh0.0>=2018.9.0 and <2018.9.1.1 or >=2018.6.0 and <2018.6.1.2 or >=2011.0.0 and <2017.12.4.1 or >=5.4.0 and <5.4.12.1 or >=5.3.0 and <5.3.12.42018.9.1.1, 2018.6.1.2, 2017.12.4.1, 5.4.12.1
GHSA-pqjm-xcp8-wgmmEz Platform and Legacy are prone to an insecure interpretation of PHP/PHAR uploadsmedium0.0>=2018.9.0 and <2018.9.1.3 or >=2018.6.0 and <2018.6.1.4 or >=2011.0.0 and <2017.12.4.3 or >=5.4.0 and <5.4.12.3 or >=5.3.0 and <5.3.12.62018.9.1.3, 2018.6.1.4, 2017.12.4.3, 5.4.12.3

Am I affected?

Find out in one command. phpwarden checks your composer.lock against this advisory and 20,000+ others, ranked by real-world exploitation (CISA KEV + EPSS). Free, offline, open data.

# one-time install
pip install phpwarden

# then
phpwarden deps composer.lock

Or keep it checked automatically: GitHub Action · pre-commit hook · GitLab CI · Laravel artisan command

Install docs   How findings are ranked
A version is vulnerable when it falls inside an affected range and below the fixed version. phpwarden applies these ranges to the exact versions in your lockfile or install, so you only see what applies to you.