Is phpoffice/common 0.2 vulnerable?

Composer · 9 releases from 0.2.0 to 0.2.9 · latest phpoffice/common is 1.1.0 · checked 18 Nov 2026

No known advisories in the last release

phpoffice/common 0.2.9, the last 0.2 release, has no known advisories. 1 advisory affects earlier 0.2.x releases, so update to 0.2.9.

Update within 0.2: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

Fixed within 0.2.x, affecting earlier releases

  • 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.2.x release

Affected: 0.2.0 to 0.2.8. 0.2.9 is not affected. Latest phpoffice/common: 1.1.0.

VersionKnown advisories
phpoffice/common 0.2.9None
phpoffice/common 0.2.8CVE-2018-14065
phpoffice/common 0.2.7CVE-2018-14065
phpoffice/common 0.2.6CVE-2018-14065
phpoffice/common 0.2.5CVE-2018-14065
phpoffice/common 0.2.3CVE-2018-14065
phpoffice/common 0.2.2CVE-2018-14065
phpoffice/common 0.2.1CVE-2018-14065
phpoffice/common 0.2.0CVE-2018-14065

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

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.