cve.bz

CVE-2026-54180 laravel-backpack crud: Incorrect Authorization

7.6 highEPSS 0.5%Fix available

High (7.6) in laravel-backpack crud. EPSS 0.5% estimated probability of exploitation activity in the next 30 days. Fixed in backpack/crud 6.8.14, 7.0.38.

On this page
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.

Severity

CVSS 3.1

7.6 high
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:H/A:L
EPSS
0.5% (unchanged from 0.5% a week ago; 0.5% 30 days ago) estimated probability of exploitation activity in the next 30 days; 41st percentile. Scored 2026-11-17. A forecast for this CVE across the internet, not for your own systems.
CISA's assessment (SSVC)
Exploitation: none · Automatable: no · Technical impact: partial, assessed 2026-09-14. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
CWEs
CWE-639 Authorization Bypass Through User-Controlled Key
CWE-863 Incorrect Authorization
OWASP Top 10
A01:2025 Broken Access Control
Published
Modified
NVD analysis
Deferred: the NVD does not plan to analyze it
Record from
the NVD, synced

Fix and patched versions

  • backpack/crud (Packagist): fixed in 6.8.14, 7.0.38

Ask an AI about this CVE

Show the promptExplain CVE-2026-54180 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-54180?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-54180?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2026-54180 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Affected

Versions

From the CNA's record in the CVE List.

ProductAffected
Laravel-Backpack CRUD>= 6.0.0, < 6.8.14
Laravel-Backpack CRUD>= 7.0.0, < 7.0.38

Packages (OSV)

AdvisoryEcosystemPackageAffectedFixed in
GHSA-vgmv-8xjc-6rchPackagistbackpack/crud>=6.0.0 <6.8.146.8.14
GHSA-vgmv-8xjc-6rchPackagistbackpack/crud>=7.0.0 <7.0.387.0.38

References

Check your stackJSON