CVE-2026-54180: High severity composer/backpack/crud vulnerability
Summary
Backpack CRUD's list and read operations correctly apply any query scopes registered via addClause() / addBaseClause() (e.g. tenant isolation, user ownership). However, the Update, Delete, and Reorder operations bypassed these scopes, fetching records directly from the unscoped model query.
An authenticated user who knows or can guess a record's primary key could therefore update, delete, or reorder records that should be invisible to them — a classic IDOR on write paths.
Applications that rely on addBaseClause for row-level access control (multi-tenancy, per-user data isolation) are affected.
Impact
Any Backpack CRUD panel that uses addBaseClause or addClause to restrict which rows a user may access is affected on its write operations. An authenticated low-privilege user can modify or delete records belonging to other tenants / users.
Patches
Apply the fixed release for your major version:
- v6: upgrade to 6.8.14 or later - v7: upgrade to 7.0.38 or later
The fix ensures Update, Delete, and Reorder all resolve records through the same scoped query used by the read side.
Workarounds
If you cannot upgrade immediately, add explicit Gate / Policy checks in your CrudController's update(), destroy(), and reorder() methods to verify the authenticated user is permitted to act on the resolved record.
Credits
Reported by Vishal Shukla (@shukla304).
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade
composer/backpack/crudto a version that resolves this vulnerability.Fixed in 7.0.38 - Upgrade
Upgrade
composer/backpack/crudto a version that resolves this vulnerability.Fixed in 6.8.14 - Upgrade
Upgrade to a fixed release to a version that resolves this vulnerability.
Fixed in 6.8.14 - Upgrade
Upgrade to a fixed release to a version that resolves this vulnerability.
Fixed in 7.0.38 - Configuration
If you cannot upgrade immediately, add explicit Gate/Policy checks in your Backpack CRUD write paths to ensure the authenticated user is permitted to act on the resolved record, especially where `addBaseClause` / `addClause` scopes could be bypassed.
Backpack CRUD (authorization workaround) Gate/Policy checks on write operations (Update/Delete/Reorder) = Add explicit Gate/Policy checks in your Backpack CRUD controller/model layer
Event History
Frequently Asked Questions
Which deployments are exposed?
Backpack CRUD panels that use addBaseClause or addClause for row-level restrictions are affected on write operations. This includes applications using those clauses for multi-tenant separation or per-user ownership controls.
What does an attacker need to exploit this issue?
An attacker must be authenticated as a low-privilege user and know or be able to guess another record's primary key. They can then target records that should be outside their permitted scope.
Which actions bypass the configured row-level scopes?
Update, Delete, and Reorder operations bypassed the scoped query and fetched records through an unscoped model query. List and read operations correctly apply the registered scopes.
What versions contain the fix?
Upgrade Backpack CRUD v6 to 6.8.14 or later, or v7 to 7.0.38 or later. The fix applies the same scoped query used for reads to Update, Delete, and Reorder operations.