Is maestroerror/php-heic-to-jpg 0.3 vulnerable?
Composer · 3 releases from 0.3.0 to 0.3.2 · 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.3.2, the last 0.3 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.
composer require maestroerror/php-heic-to-jpg:^1.0.5Is your project on an affected maestroerror/php-heic-to-jpg?
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.3.2
Remote code execution in php-heic-to-jpg
- Affected
- <1.0.5
- Fixed in
- 1.0.5
Every maestroerror/php-heic-to-jpg 0.3.x release
Affected: 0.3.0 to 0.3.2. Latest maestroerror/php-heic-to-jpg: 1.0.8.
| Version | Known advisories |
|---|---|
| maestroerror/php-heic-to-jpg 0.3.2 | CVE-2024-48514 |
| maestroerror/php-heic-to-jpg 0.3.1 | CVE-2024-48514 |
| maestroerror/php-heic-to-jpg 0.3.0 | CVE-2024-48514 |
Which of your client projects are still on maestroerror/php-heic-to-jpg 0.3?
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.