# CVE-2026-54180: backpack/crud: CRUD panel query scopes are not enforced on Update, Delete, and Reorder (cross-tenant IDOR)

> Authenticated users can modify, delete, or reorder records outside their authorized scope by bypassing query restrictions in the Backpack CRUD package.

- **Severity:** High 7.6 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:H/A:L`)
- **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-vgmv-8xjc-6rch

## What is CVE-2026-54180?

CVE-2026-54180 is a high-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.14 and 7.0.38, the Update, Delete, and Reorder operations resolve records from the unscoped model query instead of the query configured through addClause() or addBaseClause(). An authenticated user who knows or guesses an out-of-scope record primary key can therefore modify, delete, or reorder records hidden by tenant, ownership, or other row-level access-control scopes. Applications that do not rely on CRUD query clauses for authorization are not affected by this specific bypass. The fix routes all three write operations through getModelWithCrudPanelQuery(), matching the scoped list and read behavior. This issue is fixed in versions 6.8.14 and 7.0.38.

Weakness: CWE-863 (Incorrect Authorization), CWE-639 (Authorization Bypass Through User-Controlled Key)

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

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.14 |
| `backpack/crud` | Packagist | From 6.0.0 | 6.8.14 |
| `backpack/crud` | Packagist | From 7.0.0 | 7.0.38 |
| `backpack/crud` | Packagist | From 7.0.0 | 7.0.38 |

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

Upgrade backpack/crud to a fixed version for your release line: 6.8.14 or 7.0.38.

## Is CVE-2026-54180 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-54180 is a high-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-54180 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.14
- backpack/crud (Packagist): affected from 6.0.0; fixed in 6.8.14
- backpack/crud (Packagist): affected from 7.0.0; fixed in 7.0.38
- backpack/crud (Packagist): affected from 7.0.0; fixed in 7.0.38

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

## Sources

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

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