backpack/crud: HasMany/MorphMany relation fields allow cross-tenant record re-parenting (IDOR) via attachManyRelation

Summary

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.15 and 7.0.47, HasMany and MorphMany handling through attachManyRelation during CRUD create and update operations accepts submitted child primary keys without consistently restricting updates to records belonging to the current parent or permitted by the developer-defined relation scope. An authenticated low-privilege administrator who can edit a parent form exposing an affected multiple-relation field can cause unrelated child records to be reassigned, detached, nulled, or deleted across ownership or tenant boundaries. Exploitation requires related records that should not be attachable or removable by that administrator and the absence of additional application-level authorization around submitted relation values. This issue is distinct from earlier direct main-entity CRUD scoping fixes because it affects secondary models modified by relationship-saving logic. This issue is fixed in versions 6.8.15 and 7.0.47.

Timeline

1. Sep 14, 2026, 5:51 PM UTCCVE published
2. Sep 14, 2026, 6:10 PM UTCCISA SSVC assessment

   Exploitation: none · Automatable: no · Technical impact: partial

3. Sep 14, 2026, 6:11 PM UTCRecord last updated

Affected versions

• Laravel-Backpack CRUD

  From 6.0.0 · fixed in 6.8.15; From 7.0.0 · fixed in 7.0.47

• backpack/crudPackagist

  From 7.0.0 · fixed in 7.0.47

• backpack/crudPackagist

  From 6.0.0 · fixed in 6.8.15

References 7