Is maestroerror/php-heic-to-jpg 1.0 vulnerable?

Composer · 9 releases from 1.0.0 to 1.0.8 · latest maestroerror/php-heic-to-jpg is 1.0.8 · checked 18 Nov 2026

No known advisories in the last release

maestroerror/php-heic-to-jpg 1.0.8, the last 1.0 release, has no known advisories. 1 advisory affects earlier 1.0.x releases, so update to 1.0.8.

Update within 1.0:composer require maestroerror/php-heic-to-jpg:^1.0.8

Is your project on an affected maestroerror/php-heic-to-jpg?

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

  • HighCVE-2024-48514GHSA-g8v9-c8m3-942v24 Oct 2024

    Remote code execution in php-heic-to-jpg

    Affected
    <1.0.5
    Fixed in
    1.0.5

Every maestroerror/php-heic-to-jpg 1.0.x release

Affected: 1.0.0 to 1.0.4. 1.0.5 and later are not affected.

VersionKnown advisories
maestroerror/php-heic-to-jpg 1.0.8None
maestroerror/php-heic-to-jpg 1.0.7None
maestroerror/php-heic-to-jpg 1.0.6None
maestroerror/php-heic-to-jpg 1.0.5None
maestroerror/php-heic-to-jpg 1.0.4CVE-2024-48514
maestroerror/php-heic-to-jpg 1.0.3CVE-2024-48514
maestroerror/php-heic-to-jpg 1.0.2CVE-2024-48514
maestroerror/php-heic-to-jpg 1.0.1CVE-2024-48514
maestroerror/php-heic-to-jpg 1.0.0CVE-2024-48514

Which of your client projects are still on maestroerror/php-heic-to-jpg 1.0?

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

Other maestroerror/php-heic-to-jpg 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.