Is mikehaertl/php-shellcommand 1.4 vulnerable?

Composer · 2 releases from 1.4.0 to 1.4.1 · latest mikehaertl/php-shellcommand is 1.7.0 · checked 18 Nov 2026

Yes: 1 known advisory

Yes. mikehaertl/php-shellcommand 1.4.1, the last 1.4 release, is affected by 1 known security advisory (1 critical), including CVE-2019-10774. Upgrade to 1.6.1 or later to fix all of them.

Upgrade with:composer require mikehaertl/php-shellcommand:^1.6.1

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

Advisories affecting mikehaertl/php-shellcommand 1.4.1

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

Affected: 1.4.0 to 1.4.1. Latest mikehaertl/php-shellcommand: 1.7.0.

VersionKnown advisories
mikehaertl/php-shellcommand 1.4.1CVE-2019-10774
mikehaertl/php-shellcommand 1.4.0CVE-2019-10774

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

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.