Is mikehaertl/php-shellcommand 1.6 vulnerable?

Composer · 5 releases from 1.6.0 to 1.6.4 · latest mikehaertl/php-shellcommand is 1.7.0 · checked 18 Nov 2026

No known advisories in the last release

mikehaertl/php-shellcommand 1.6.4, the last 1.6 release, has no known advisories. 1 advisory affects earlier 1.6.x releases, so update to 1.6.4.

Update within 1.6:composer require mikehaertl/php-shellcommand:^1.6.4

Is your project on an affected mikehaertl/php-shellcommand?

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 1.6.x, affecting earlier releases

  • CriticalCVE-2019-10774GHSA-c7fv-wv9f-cgjw24 May 2022

    php-shellcommand command injection vulnerability

    Affected
    <1.6.1
    Fixed in
    1.6.1

Every mikehaertl/php-shellcommand 1.6.x release

Affected: 1.6.0. 1.6.1 and later are not affected. Latest mikehaertl/php-shellcommand: 1.7.0.

VersionKnown advisories
mikehaertl/php-shellcommand 1.6.4None
mikehaertl/php-shellcommand 1.6.3None
mikehaertl/php-shellcommand 1.6.2None
mikehaertl/php-shellcommand 1.6.1None
mikehaertl/php-shellcommand 1.6.0CVE-2019-10774

Which of your client projects are still on mikehaertl/php-shellcommand 1.6?

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

Other mikehaertl/php-shellcommand 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.