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

> Authenticated administrators can reassign or delete unrelated child records across tenant boundaries via insecure relation handling in Backpack CRUD.

- **Severity:** Medium 6.5 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 14 Sep 2026
- **Updated:** 14 Sep 2026
- **Also known as:** GHSA-42vx-43vc-x6pr

## What is CVE-2026-57570?

CVE-2026-57570 is a medium-severity missing authorization vulnerability in Laravel-Backpack CRUD, published on 14 Sep 2026. Any signed-in user can exploit it over the network, 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.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.

Weakness: CWE-862 (Missing Authorization)

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

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.15 |
| `backpack/crud` | Packagist | From 6.0.0 | 6.8.15 |
| `backpack/crud` | Packagist | From 7.0.0 | 7.0.47 |
| `backpack/crud` | Packagist | From 7.0.0 | 7.0.47 |

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

Upgrade backpack/crud to a fixed version for your release line: 6.8.15 or 7.0.47.

## Is CVE-2026-57570 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-57570 is a medium-severity missing authorization vulnerability in Laravel-Backpack CRUD, published on 14 Sep 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-57570 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.15
- backpack/crud (Packagist): affected from 6.0.0; fixed in 6.8.15
- backpack/crud (Packagist): affected from 7.0.0; fixed in 7.0.47
- backpack/crud (Packagist): affected from 7.0.0; fixed in 7.0.47

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-57570/ (Markdown: https://insights.sbomify.com/CVE-2026-57570/index.md)
```

## Sources

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

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