Skip to content

← Public intelligence

Packagist package

phpoffice/phpexcel

Open actionable advisories and recorded vendor fixes. This public package view has no inventory attached and cannot establish whether your deployment is affected. A vendor fix never resolves your finding; verify your installed version and the source guidance.

Open advisories

3 actionable advisories, newest first. Withdrawn advisories and news are excluded. Coverage is partial.

  1. High, CVSS 8.7PackagistPublished

    PHPExcel XXE Vulnerability

    CVE-2015-3542 · GHSA-3m9x-2qfj-xvq4

    Affected
    • Packagist phpoffice/phpexcel < 1.8.1
    Fixed in
    1.8.1· Vendor fix available
    Issue
    PHPExcel XXE Vulnerability

    Recommended action: Upgrade to 1.8.1 or later, then redeploy and verify.A vendor fix does not resolve your finding until you verify it in your own systems.

    Sources:github.comSource checked Evidence →
  2. UnratedPackagistPublished

    PHPExcel vulnerable to XXE attacks through libxml

    CVE-2014-2054 · GHSA-28rm-rj57-qjpv

    Affected
    • Packagist phpoffice/phpexcel < 1.8.0
    Fixed in
    1.8.0· Vendor fix available
    Issue
    PHPExcel before 1.8.0, as used in ownCloud Server before 5.0.15 and 6.0.x before 6.0.2, does not disable external entity loading in libxml, which allows remote attackers to read arbitrary files, cause a denial of service, or possibly have other impact via an XML External Entity (XXE) attack.

    Recommended action: Upgrade to 1.8.0 or later, then redeploy and verify.A vendor fix does not resolve your finding until you verify it in your own systems.

    Sources:github.comSource checked Evidence →
  3. High, CVSS 8.8PackagistPublished

    XXE in PHPSpreadsheet due to encoding issue

    CVE-2018-19277 · GHSA-xcrg-29h7-h4cj

    Affected
    • Packagist phpoffice/phpexcel < 1.8.2
    Fixed in
    1.8.2· Vendor fix available
    Issue
    securityScan() in PHPOffice PhpSpreadsheet through 1.5.0 allows a bypass of protection mechanisms for XXE via UTF-7 encoding in a .xlsx file

    Recommended action: Upgrade to 1.8.2 or later, then redeploy and verify.A vendor fix does not resolve your finding until you verify it in your own systems.

    Sources:github.comSource checked Evidence →