# CVE-2026-54177: Laravel Backpack CRUD: HasUploadFields keeps the attacker-supplied file extension — public-disk uploads of `shell.php` reach the webserver

> An authenticated administrator can achieve remote code execution by uploading executable files if application-level validation is missing and public disk access is enabled.

- **Severity:** Medium 6.6 (`CVSS:3.1/AV:N/AC:H/PR:H/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 14 Sep 2026
- **Updated:** 16 Sep 2026
- **Also known as:** GHSA-8q2w-pv9p-mjvc

## What is CVE-2026-54177?

CVE-2026-54177 is a medium-severity vulnerability in Laravel-Backpack CRUD, published on 14 Sep 2026. An attacker needs administrator access to exploit it, with no action from the victim.

### Official description

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.

Weakness: CWE-434 (Unrestricted Upload of File with Dangerous Type)

## Which versions are affected by CVE-2026-54177?

4 open source packages ship an affected version, including backpack/crud.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `backpack/crud` | Packagist | From 6.0.0 | 6.8.14 |
| `backpack/crud` | Packagist | From 6.0.0 | 6.8.14 |
| `backpack/crud` | Packagist | From 7.0.0 | 7.0.38 |
| `backpack/crud` | Packagist | From 7.0.0 | 7.0.38 |

## How do I fix CVE-2026-54177?

Upgrade backpack/crud to a fixed version for your release line: 6.8.14 or 7.0.38.

## Is CVE-2026-54177 being exploited?

There is no known exploitation of CVE-2026-54177 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-54177 and fix it if it is affected.

What it is: CVE-2026-54177 is a medium-severity vulnerability in Laravel-Backpack CRUD, published on 14 Sep 2026. An attacker needs administrator access to exploit it, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-54177 in the wild and no public exploit code.

Affected packages and fixed versions:
- backpack/crud (Packagist): affected from 6.0.0; fixed in 6.8.14
- backpack/crud (Packagist): affected from 6.0.0; fixed in 6.8.14
- backpack/crud (Packagist): affected from 7.0.0; fixed in 7.0.38
- backpack/crud (Packagist): affected from 7.0.0; fixed in 7.0.38

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-54177/ (Markdown: https://insights.sbomify.com/CVE-2026-54177/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-54177
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-54177
- OSV: https://osv.dev/vulnerability/CVE-2026-54177

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-54177/
Summaries are generated and may contain mistakes; the official description above is the record.