Is backpack/crud 5.4 vulnerable?
Composer · 17 releases from 5.4.0 to 5.4.16 · latest backpack/crud is 7.1.26 · checked 18 Nov 2026
Yes: 3 known advisories
Yes. backpack/crud 5.4.16, the last 5.4 release, is affected by 3 known security advisories (3 high), including CVE-2026-54182, CVE-2026-54178, CVE-2026-54175. Upgrade to 6.8.12 or later to fix all of them.
composer require backpack/crud:^6.8.12Is your project on an affected backpack/crud?
Look after several Laravel or PHP apps? Indie watches up to 15 repos, private ones too, for $5 a month. See Indie
Advisories affecting backpack/crud 5.4.16
Laravel Backpack CRUD: OS command injection in Stats::makeCurlRequest via attacker-controlled Host header (pre-auth)
- Affected
- >=4.1.0 <4.1.72 · >=5.0.0 <5.6.2 · >=6.0.0 <6.8.13 · >=7.0.0 <7.0.36
- Fixed in
- 4.1.72, 5.6.2, 6.8.13, 7.0.36
Laravel Backpack CRUD: Arbitrary file deletion via attacker-controlled clear_<attr>[] in HasUploadFields::uploadMultipleFilesToDisk
- Affected
- >=5.0.0 · >=6.0.0 <6.8.12 · >=7.0.0 <7.0.35
- Fixed in
- 6.8.12, 7.0.35
Laravel Backpack CRUD: Unverified password change in MyAccountController via mass assignment
- Affected
- <6.8.11 · >=7.0.0-alpha.1 <7.0.34
- Fixed in
- 6.8.11, 7.0.34
Every backpack/crud 5.4.x release
Affected: 5.4.0 to 5.4.16. Latest backpack/crud: 7.1.26.
| Version | Known advisories |
|---|---|
| backpack/crud 5.4.16 | CVE-2026-54182, CVE-2026-54178, CVE-2026-54175 |
| backpack/crud 5.4.15 | CVE-2026-54182, CVE-2026-54178, CVE-2026-54175 |
| backpack/crud 5.4.14 | CVE-2026-54182, CVE-2026-54178, CVE-2026-54175 |
| backpack/crud 5.4.13 | CVE-2026-54182, CVE-2026-54178, CVE-2026-54175 |
| backpack/crud 5.4.12 | CVE-2026-54182, CVE-2026-54178, CVE-2026-54175 |
| backpack/crud 5.4.11 | CVE-2026-54182, CVE-2026-54178, CVE-2026-54175 |
| backpack/crud 5.4.10 | CVE-2026-54182, CVE-2026-54178, CVE-2026-54175 |
| backpack/crud 5.4.9 | CVE-2026-54182, CVE-2026-54178, CVE-2026-54175 |
| backpack/crud 5.4.8 | CVE-2026-54182, CVE-2026-54178, CVE-2026-54175 |
| backpack/crud 5.4.7 | CVE-2026-54182, CVE-2026-54178, CVE-2026-54175 |
| backpack/crud 5.4.6 | CVE-2026-54182, CVE-2026-54178, CVE-2026-54175 |
| backpack/crud 5.4.5 | CVE-2026-54182, CVE-2026-54178, CVE-2026-54175 |
| backpack/crud 5.4.4 | CVE-2026-54182, CVE-2026-54178, CVE-2026-54175 |
| backpack/crud 5.4.3 | CVE-2026-54182, CVE-2026-54178, CVE-2026-54175 |
| backpack/crud 5.4.2 | CVE-2026-54182, CVE-2026-54178, CVE-2026-54175 |
| backpack/crud 5.4.1 | CVE-2026-54182, CVE-2026-54178, CVE-2026-54175 |
| backpack/crud 5.4.0 | CVE-2026-54182, CVE-2026-54178, CVE-2026-54175 |
Which of your client projects are still on backpack/crud 5.4?
NPMscan reads the lockfiles in every GitHub repo you pick, finds the exact backpack/crud version each one installs, and checks it against these advisories. Each finding comes with the command that fixes it.
Other backpack/crud 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.