CVE-2026-57570: Laravel Backpack CRUD: HasMany/MorphMany relation fields allow cross-tenant record re-parenting (IDOR) via attachManyRelation
Vulnerability Details Affected area: HasMany / MorphMany relation handling during CRUD create and update operations CWE: CWE-862 — Missing Authorization Severity: Medium CVSS: 6.5 — CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:N Summary Backpack CRUD contained an authorization issue in the way certain HasMany and MorphMany relationship fields were processed during create and update operations.
Published Aug 20, 2026
Affected packages
backpack/crud
- Ecosystem
- Composer (PHP)
- Affected
- >= 7.0.0, < 7.0.47
- Fixed in
- 7.0.47
- Check
composer show backpack/crud
backpack/crud
- Ecosystem
- Composer (PHP)
- Affected
- >= 6.0.0, < 6.8.15
- Fixed in
- 6.8.15
- Check
composer show backpack/crud
Advisory details
From the GitHub Advisory Database (CC BY 4.0).
Vulnerability Details
Affected area: HasMany / MorphMany relation handling during CRUD create and update operations CWE: CWE-862 — Missing Authorization Severity: Medium CVSS: 6.5 — CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:N
Summary
Backpack CRUD contained an authorization issue in the way certain HasMany and MorphMany relationship fields were processed during create and update operations.
When an admin form allowed users to manage multiple related records, Backpack could update related model records based on submitted primary keys without sufficiently checking whether those records were eligible to be associated with the current parent model.
This could allow an authenticated, low-privileged admin user to affect related records outside the intended authorization or tenancy boundary, if the affected CRUD form exposed this type of relationship field.
Root Cause
The vulnerable logic processed submitted relationship values and updated matching related records without consistently limiting those updates to records that already belonged to the current parent model, or to records allowed by the developer-defined relation scope.
As a result, a user with permission to edit one parent record could potentially cause unrelated child records to be reassigned, detached, nulled, or deleted as a side effect of saving the form.
This issue is separate from earlier fixes that scoped direct CRUD operations on the main entity. Those protections covered the model being directly edited, but they did not fully cover secondary models modified through relationship-saving logic.
Impact
An authenticated admin user with access to an affected CRUD operation could potentially cause unauthorized changes to related records.
Possible impact includes:
- Unauthorized reassignment of related records across users, parents, or tenants.
- Unauthorized detachment or removal of related records.
- Data integrity issues in multi-tenant or permission-sensitive applications.
The issue requires an authenticated admin account with edit access to a CRUD entity that exposes an affected HasMany or MorphMany multiple-relation field.
Affected Conditions
An application may be affected when all of the following are true:
- A Backpack CRUD form exposes a multiple-selection field for a HasMany or MorphMany relation.
- The related model contains records that should not be attachable or removable by the current admin user.
- The application relies on tenant, ownership, or authorization boundaries for those related records.
- The application has not added its own additional validation or authorization checks around submitted relation values.
Recommended Fix
Backpack should scope relationship attach and detach operations so they only affect records that are valid for the current parent model and relation context.
The fix should ensure that related records are filtered through the relation’s intended query scope, ownership rules, or other developer-defined constraints before any update, detach, null, or delete operation occurs.
Applications using affected relationship fields should also validate submitted relation IDs server-side, especially in multi-tenant or permission-sensitive admin panels.
Verification
The issue was confirmed through an internal PHPUnit test against Backpack’s existing Testbench fixtures.
The test demonstrated that, before the fix, a related record owned by one parent model could be reassigned to another parent model through the relationship-saving flow, without an explicit ownership or authorization check.
After applying the fix, submitted relationship values are constrained before related records are modified, preventing unauthorized reassignment or removal.
Credited to iaohkut-from-NightWolf-Team, pxpm, tabacitu.
References
How this page is made: the data panel comes from the GitHub Advisory Database, CISA’s KEV catalog, the NVD and FIRST EPSS, and updates twice a day. No analysis has been written for this entry yet. Methodology
More Composer (PHP) vulnerabilities
All Composer (PHP) entriesCVE-2026-54175
Laravel Backpack CRUD: Unverified password change in MyAccountController via mass assignment
high7.6Aug 20, 2026CVE-2026-54176
Laravel Backpack CRUD: MyAccountController allows changing the login email without a current-password check
medium6.5Aug 20, 2026CVE-2026-54177
Laravel Backpack CRUD: HasUploadFields keeps the attacker-supplied file extension — public-disk uploads of `shell.php` reach the webserver
medium6.6Aug 20, 2026CVE-2026-54178
Laravel Backpack CRUD: Arbitrary file deletion via attacker-controlled clear_<attr>[] in HasUploadFields::uploadMultipleFilesToDisk
high8.1No fixAug 20, 2026CVE-2026-54179
Laravel Backpack CRUD: SingleBase64Image accepts any base64 payload behind a `data:image` prefix — SVG-with-script lands on the public disk
medium4.4Aug 20, 2026CVE-2026-54180
Laravel Backpack CRUD: CRUD panel query scopes are not enforced on Update, Delete, and Reorder (cross-tenant IDOR)
high7.6Aug 20, 2026
