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

Composer · 1 release from 0.1.0 to 0.1.0 · latest maestroerror/php-heic-to-jpg is 1.0.8 · checked 18 Nov 2026

Yes: 1 known advisory

Yes. maestroerror/php-heic-to-jpg 0.1.0, the last 0.1 release, is affected by 1 known security advisory (1 high), including CVE-2024-48514. Upgrade to 1.0.5 or later to fix all of them.

Upgrade with:composer require maestroerror/php-heic-to-jpg:^1.0.5

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

Advisories affecting maestroerror/php-heic-to-jpg 0.1.0

  • 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

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

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.