backpack/crud security advisory

CVE-2026-54178: Laravel Backpack CRUD: Arbitrary file deletion via attacker-controlled clear_<attr>[] in HasUploadFields::uploadMultipleFilesToDisk

CVE-2026-54178 is a high-severity arbitrary file deletion vulnerability in the PHP package backpack/crud (CVSS 8.1), published 14 September 2026. It is fixed in 6.8.12 and 7.0.35, one per release line; earlier versions on each line are affected. Exploiting it needs a low-privilege user account.

high 8.1 published 2026-09-14 · updated 2026-09-30

Affected versions: >= 5.0.0, < 6.8.12
>= 7.0.0, < 7.0.35
Fixed in: 6.8.12, 7.0.35
Newest release: 7.1.24
Severity: High · CVSS 8.1
Type: Arbitrary file deletion
CWE-22, CWE-285, CWE-639
Exploited in the wild: Not on the CISA KEV list
checked 2026-11-04

Is your backpack/crud version affected?

Run composer show backpack/crud in your project, then enter the version. We check it against this and every other known backpack/crud advisory.

Who can exploit CVE-2026-54178

Access: A normal, low-privilege user account in the app.

CVSS vector (scored by GitHub): CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:H

Your app is only exposed if it uses the affected part of backpack/crud. The advisory below says which part that is. If you are not sure, upgrade anyway: it costs less than finding out.

How to fix CVE-2026-54178 in backpack/crud

Find the installed version: composer show backpack/crud. If you never required it yourself, composer why backpack/crud shows which package pulls it in.
Update it: composer update backpack/crud --with-all-dependencies. You need the fixed version for your release line (6.8.12 and 7.0.35).
If Composer will not go that high, your composer.json constraint is holding it back. Widen it (for example "backpack/crud": "^7.0.35" if you can take that version), or upgrade the package that requires it.
Run composer audit. It reads the same advisory data and should no longer list CVE-2026-54178.
Commit composer.lock and deploy it. On the server, run composer install --no-dev from the lock file, not composer update.

If you cannot upgrade yet

General hardening for arbitrary file deletion issues while the upgrade waits. None of it replaces the fix.

Validate file names against an allow-list and reject paths containing ../ or absolute paths.
If your app does not use the affected feature, note that in your audit, but still plan the upgrade.

The CVE-2026-54178 advisory

backpack/crud provides Create, Read, Update & Delete (CRUD) functions for Backpack, a collection of Laravel packages that help users build custom administration panels. Prior to 6.8.12 and 7.0.35, HasUploadFields::uploadMultipleFilesToDisk in src/app/Models/Traits/HasUploadFields.php trusts disk-relative paths from clear_<attribute>[] and passes them to Storage::disk()->delete without confirming that the paths are persisted on the current model record. An authenticated user with Update access to a CRUD using this mutator through src/app/Models/Traits/CrudTrait.php can delete another record's attachment, a shared asset, or another operational file on the configured disk by submitting its path. The newer MultipleFiles uploader is not affected because it intersects requested deletions with the record's persisted file list. This flaw does not permit reading the deleted files. The 5.x line remains affected through its final releases. This issue is fixed in versions 6.8.12 and 7.0.35.

Description from the CVE record, published by GitHub (the CVE Numbering Authority), via the NVD entry for CVE-2026-54178. Advisory title: “Laravel Backpack CRUD: Arbitrary file deletion via attacker-controlled clear_<attr>[] in HasUploadFields::uploadMultipleFilesToDisk”.

References

GitHub advisory GHSA-8xjm-wqrp-2f25 github.com
Fix commit 0c7e095 github.com
Fix commit baae042 github.com
Pull request #5982 github.com
Pull request #5983 github.com
Release 6.8.12 github.com
Release 7.0.35 github.com

Other backpack/crud advisories

Need help patching or upgrading? Laskyr does PHP and Laravel security fixes and upgrades. Tell us what you run and we reply with a plan and a price.

Ask about a fix

Where this data comes from

Affected and fixed versions: the Packagist security advisories API (GitHub Advisory Database and FriendsOfPHP), the same data composer audit uses. Synced 2026-11-03.
Description, score, weakness and references: NIST National Vulnerability Database (NVD), checked 2026-11-04. This product uses data from the NVD API but is not endorsed or certified by the NVD.
Exploited-in-the-wild status: the CISA Known Exploited Vulnerabilities catalog, checked 2026-11-04.
Compiled by Daniel Lasek at Laskyr from the sources above. The summary, “who can exploit it”, “how to fix it” and hardening sections are our plain-English reading of the record and are generated from it. The quoted description is the record's own text. Spot an error? Tell us.