Answer in brief
CVE-2026-54177 records a Medium severity (CVSS 6.6) vulnerability in backpack/crud: HasUploadFields keeps the attacker-supplied file extension — public-disk uploads of `shell.php` reach the webserver. The current sources do not mark it as known exploited. The current feed maps backpack/crud (composer), backpack/crud (composer), Laravel-Backpack/CRUD (generic), backpack/crud (packagist) and additional mapped packages. Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
CVSS is 6.6. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps backpack/crud (composer), backpack/crud (composer), Laravel-Backpack/CRUD (generic), backpack/crud (packagist) and additional mapped packages. Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| backpack/crudcomposer | >=6.0.0,<6.8.14 | 6.8.14 |
| backpack/crudcomposer | >=7.0.0,<7.0.38 | 7.0.38 |
| Laravel-Backpack/CRUDgeneric | >= 6.0.0, < 6.8.14 || >= 7.0.0, < 7.0.38 | Not reported |
| backpack/crudpackagist | >=6.0.0 <6.8.14 | 6.8.14 |
| backpack/crudpackagist | >=7.0.0 <7.0.38 | 7.0.38 |
Published upstream
Sep 14, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Sep 14, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Aug 20, 2026
backpack/crud provides Create, Read, Update & Delete (CRUD) functions for Backpack, a collection of Laravel packages that help users build custom administration panels. From 6.0.0 until 6.8.14 and 7.0.38, HasUploadFields methods uploadFileToDisk and uploadMultipleFilesToDisk, used through CrudTrait, and the withFiles() path through FileNameGenerator do not internally reject server-executable file types. An authenticated administrator can achieve remote code execution by using an upload-enabled CRUD field without mimes: and mimetypes: validation when the public disk is web-accessible through php artisan storage:link and the web-server and PHP-FPM configuration executes the stored extension. The legacy path preserves an accepted extension and the newer path derives an extension without blocking dangerous types. The package-level restriction is defense in depth and does not replace application-level upload validation. This issue is fixed in versions 6.8.14 and 7.0.38.
Quoted source text, attributed separately from HOL analysis.