By Null Ventures MCP platform
Menu

vulnerability / NVI-00003391 / Revision 4

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

OSV carries this publisher advisory for ezsystems/ezpublish-kernel, ezsystems/ezpublish-legacy, ezsystems/ezpublish-kernel, ezsystems/ezpublish-kernel, ezsystems/ezpublish-legacy. This is an aggregated source copy; consult the original publisher and compare update dates.

source listedactiveGHSA-54p5-gxq6-j98gCVE-2020-10806

This report has not inspected your inventory, configuration, deployed build, reachability or evidence. A catalog listing and a severity score do not establish exposure or compromise.

01 / Meaning

Why it matters

Published affected context helps an owner decide what evidence to gather. This report has not examined your application.

EPSS

2.320%

FIRST EPSS model v2026.06.15; exploitation probability over 30 days, percentile 0.83458. Missing scores are unknown.

As of · FIRST EPSS

02 / Applicability

The affected context

Affected versions, configuration prerequisites and known exclusions are public. Confirm each one against the deployed service.

ezsystems/ezpublish-kernel

source listed
  • ECOSYSTEM: introduced 0; fixed 5.4.14.1

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.

GitHub Advisory Database via OSV

ezsystems/ezpublish-legacy

source listed
  • ECOSYSTEM: introduced 0; fixed 5.4.14.1

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.

GitHub Advisory Database via OSV

ezsystems/ezpublish-kernel

source listed
  • ECOSYSTEM: introduced 6.0; fixed 6.13.6.2

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.

GitHub Advisory Database via OSV

ezsystems/ezpublish-kernel

source listed
  • ECOSYSTEM: introduced 7.0; fixed 7.5.6.2

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.

GitHub Advisory Database via OSV

ezsystems/ezpublish-legacy

source listed
  • ECOSYSTEM: introduced 2017; fixed 2017.12.7.2

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.

GitHub Advisory Database via OSV

ezsystems/ezpublish-legacy

source listed
  • ECOSYSTEM: introduced 2019; fixed 2019.03.4.2

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.

GitHub Advisory Database via OSV

03 / Response

What to do next

  1. vendor patch

    The original advisory lists fixed boundaries 5.4.14.1 for ezsystems/ezpublish-kernel. Confirm the publisher’s latest guidance.

    Confirm current vendor support, compatibility and deployment evidence. This report has not tested a fix in your system. GitHub Advisory Database via OSV

  2. vendor patch

    The original advisory lists fixed boundaries 5.4.14.1 for ezsystems/ezpublish-legacy. Confirm the publisher’s latest guidance.

    Confirm current vendor support, compatibility and deployment evidence. This report has not tested a fix in your system. GitHub Advisory Database via OSV

  3. vendor patch

    The original advisory lists fixed boundaries 6.13.6.2 for ezsystems/ezpublish-kernel. Confirm the publisher’s latest guidance.

    Confirm current vendor support, compatibility and deployment evidence. This report has not tested a fix in your system. GitHub Advisory Database via OSV

  4. vendor patch

    The original advisory lists fixed boundaries 7.5.6.2 for ezsystems/ezpublish-kernel. Confirm the publisher’s latest guidance.

    Confirm current vendor support, compatibility and deployment evidence. This report has not tested a fix in your system. GitHub Advisory Database via OSV

  5. vendor patch

    The original advisory lists fixed boundaries 2017.12.7.2 for ezsystems/ezpublish-legacy. Confirm the publisher’s latest guidance.

    Confirm current vendor support, compatibility and deployment evidence. This report has not tested a fix in your system. GitHub Advisory Database via OSV

  6. vendor patch

    The original advisory lists fixed boundaries 2019.03.4.2 for ezsystems/ezpublish-legacy. Confirm the publisher’s latest guidance.

    Confirm current vendor support, compatibility and deployment evidence. This report has not tested a fix in your system. GitHub Advisory Database via OSV

  7. investigate

    Identify the exact component and deployed version, examine the linked publisher’s conditions, and retain evidence of any mitigation.

    Confirm current vendor support, compatibility and deployment evidence. This report has not tested a fix in your system. FIRST EPSS

A fixed release is not deployment evidence.

Check current vendor support and compatibility. After making a change, verify the deployed build and relevant runtime conditions. Keep the evidence, owner and time. An updated lockfile alone does not prove what is running.

04 / Limits

What this report cannot establish

  • Customer inventory, deployment, reachability and exploitation have not been inspected.
  • NVD lastModified does not establish freshness of every associated CPE record.
Read the collection and interpretation limits ↗

05 / Provenance

Sources you can inspect

Each assertion retains its source. Mirrored records may repeat one underlying publisher; additional links are not independent corroboration.

  1. GHSA-54p5-gxq6-j98g ↗

    GitHub Advisory Database via OSV · vendor advisory

    Observed . GitHub-origin advisory, CC-BY-4.0; OSV is an aggregate copy, not independent corroboration.

  2. CVE-2020-10806 ↗

    NIST National Vulnerability Database · official catalog

    Observed . This product uses data from the NVD API but is not endorsed or certified by the NVD.

  3. CVE-2020-10806 ↗

    FIRST EPSS · official catalog

    Observed . FIRST EPSS; probability of exploitation in the next 30 days, not local compromise. Dataset date/model retained; FIRST services terms apply.

Public revision history

Only published revisions appear here. Routine fetches do not create a material-change event.

  1. Revision 4 ·

    Dated EPSS estimate updated; this is not a new disclosure or proof of exploitation.

  2. Revision 3 ·

    Dated EPSS estimate updated; this is not a new disclosure or proof of exploitation.

  3. Revision 2 ·

    Source facts changed; compare the preserved prior revision.

  4. Revision 1 ·

    First indexed by Null; source disclosure date is shown separately.

Read the public revision data ↗

The next step is private

Bring the question into your environment.

The connected workflow is a development preview for inventory, contextual matching, owner decisions and evidence-based verification. No system-specific result is generated by this page.

See the synthetic workflow preview ↗