Is phpoffice/common 0.1 vulnerable?

Composer · 2 releases from 0.1.0 to 0.1.1 · latest phpoffice/common is 1.1.0 · checked 18 Nov 2026

Yes: 1 known advisory

Yes. phpoffice/common 0.1.1, the last 0.1 release, is affected by 1 known security advisory (1 critical), including CVE-2018-14065. Upgrade to 0.2.9 or later to fix all of them.

Upgrade with:composer require phpoffice/common:^0.2.9

Is your project on an affected phpoffice/common?

Private repo? Upload its lockfile instead, or connect GitHub to check every repo.

Look after several Laravel or PHP apps? Indie watches up to 15 repos, private ones too, for $5 a month. See Indie

Advisories affecting phpoffice/common 0.1.1

  • CriticalCVE-2018-14065GHSA-2853-hf2g-984314 May 2022

    PHPOffice Common Improper Restriction of XML External Entity Reference

    Affected
    <0.2.9
    Fixed in
    0.2.9

Every phpoffice/common 0.1.x release

Affected: 0.1.0 to 0.1.1. Latest phpoffice/common: 1.1.0.

VersionKnown advisories
phpoffice/common 0.1.1CVE-2018-14065
phpoffice/common 0.1.0CVE-2018-14065

Which of your client projects are still on phpoffice/common 0.1?

NPMscan reads the lockfiles in every GitHub repo you pick, finds the exact phpoffice/common version each one installs, and checks it against these advisories. Each finding comes with the command that fixes it.

Other phpoffice/common versions

Advisory data from OSV.dev (opens OSV.dev in a new tab), which includes the GitHub Advisory Database. Release list from the Composer registry. Refreshed daily.