Unrestricted File Upload in backpack/crud (CVE-2026-54177)
Summary
Vulnerability in backpack/crud (CVE-2026-54177). Successful exploitation can lead to full system takeover. Exploitable via HasUploadFields. Mitigation: upgrade to 7.0.38 or later.
Original description
The description as published by the source.
Summary
HasUploadFields (used via CrudTrait on Backpack-managed models) and the withFiles() uploader preserve the client-supplied file extension without validation. On installations using a public disk with php artisan storage:link, this allows an authenticated administrator to upload a file with a server-executable extension that the web server will pass to the PHP interpreter - if no MIME or other type of upload validation is present.
Details
The uploadFileToDisk and uploadMultipleFilesToDisk methods hash the filename stem but write the client-supplied extension to disk verbatim — no allowlist, blocklist, or MIME check is applied inside the trait itself.
The newer withFiles() path (via FileNameGenerator) resolves the extension from the file's MIME type rather than the client filename, but also does not block server-executable types.
Applications that follow the Backpack quickstart without adding explicit mimes: or mimetypes: validation rules in their form requests are affected.
Impact
An authenticated administrator with access to an upload-enabled CRUD panel, on a site using the public disk with web-accessible storage and no MIME type validation, can upload a server-executable file and achieve remote code execution.
Conditions required for exploitation:
- Authenticated admin access to a Backpack CRUD panel
- An upload field with no
mimes:/mimetypes:validation rule - The
publicdisk in use (standard pattern for web-visib…
Source: GitHub Security Advisories (Global) NVD GitHub Advisory
Auto-generated summary
Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.
A vulnerability tracked as CVE-2026-54177 has been found in backpack/crud.
Attackers can target a specific entry point like HasUploadFields over the network to misuse the product.
Successful exploitation can lead to full system takeover. CVSS score: 6.6/10.
What to do: upgrade backpack/crud to 7.0.38 or later.
If unsure, ask your IT team or search "backpack/crud CVE-2026-54177" on the vendor's site.
CVE-2026-54177 (backpack/crud) — CWE-434 / CVSS v3 6.6
Attack vector: remote (network-reachable) / no user interaction
Attack surface: HasUploadFields / CrudTrait / public / uploadFileToDisk
Patched: 7.0.38 — apply immediately
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
A vulnerability (CWE-434) exists in backpack/crud. Attackers reach the vulnerable code path via HasUploadFields.
Check the vendor advisory for the affected versions of backpack/crud. Attack surface: HasUploadFields / CrudTrait / public / uploadFileToDisk.
Severity: Medium (CVSS 6.6/10). Successful exploitation can lead to full system takeover.
Update to 7.0.38.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r 'backpack/crud' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.
Response actions
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
grep -r 'backpack/crud' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
backpack/crudを grep し、稼働しているサービス・バージョンを把握する。 -
2Apply patch patch
Upgrade backpack/crud to 7.0.38ステージング環境で 7.0.38 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
3Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
Affected packages
References
- package github.com
- web github.com
- web github.com
- web github.com
- web github.com
- web github.com
- web security-advisories@github.com
- web security-advisories@github.com
- web security-advisories@github.com