CVE-2026-54180

HIGHPre-NVD 7.67.6
EchelonGraph scoreMEDIUM confidence

“—” beside the score: it is equal to the CVSS score beside it.

Score 7.6 from GitHub Security Advisory (severity: HIGH) published 2026-08-20. A secondary CVSS source baseline 7.6; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: EPSS, GitHub Security Advisory, a secondary CVSS source
Trending — 3 sources updated this week

Also known asEUVD-2026-77717 (ENISA EUVD) · GHSA-vgmv-8xjc-6rch (GitHub Security Advisories)Source: ENISA EUVD

7.6EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines (the SSVC decision on this page).
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0.5%CVSS: 7.6Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

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.

CVSS v3
7.6
EG Score
7.6HIGHmedium confidence
EG Risk
34
EG Risk 34/100

EG Risk is EchelonGraph's 0–100 priority score. It fuses impact severity (EG Severity, the CVSS base score, never the KEV-floored or EPSS-lifted EG Score) with real-world exploitation and automatability, under weights EchelonGraph set by hand, so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner.

How it’s computed (value × EchelonGraph’s weight)
Severity76% × 45%
Impact severity (EG Severity): CVSS 7.6 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation0.5% × 40%
FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.
Automatability0% × 15%
CISA's SSVC Automatable value: no (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at every mission impact level.
Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.
Action: A fix is available. Apply it within your standard update timelines.
EPSS PROB
0.5%
EPSS %ILE
39th
KEV
Not listed

What the EG score is made of (scorer v4.0: the three questions the 0–10 score mixes, published apart · methodology)

The EG score (7.6): severity, escalated by confirmed exploitation. This CVE's 7.6 is its impact severity (EG Severity), not escalated.

EG Severity
7.6 HIGHCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.GitHub Security Advisory CVSS
EG Likelihood
0.5% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-10-31). FIRST's exploitation probability, not an EchelonGraph model.
Confirmed exploitation
None on record (CISA KEV, EG-KEV Tier 1)Reported apart from the likelihood: an observed fact, not a probability.
EG Priority
SSVC Track at medium mission impactTrack at every mission impact level.CISA BOD 26-04: 60 days if the affected system is publicly exposed; Fix on system upgrade if it is not.Each input and its source, and whom BOD 26-04 binds: the SSVC and BOD 26-04 blocks below.

SSVC (CISA's decision table, applied by EchelonGraph)Track at every mission impact level.

A fix is available. Apply it within your standard update timelines.

Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table

BOD 26-04 (CISA's remediation timeline, Table 1)60 days if the affected system is publicly exposed; Fix on system upgrade if it is not.

The score's inputs: In CISA KEV no (CISA's KEV catalog) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

Published

August 20, 2026

Last Modified

September 30, 2026

Advisory Details (7)

Auto-updated Sep 14, 2026
Patch available. Sources: github, github_pr, github_commit, github_release.
GitHub release Patch Available

7.0.38 🌈

Patch available: Laravel-Backpack/CRUD 7.0.38

https://github.com/Laravel-Backpack/CRUD/releases/tag/7.0.38
GitHub release Patch Available

6.8.14 🌈

Patch available: Laravel-Backpack/CRUD 6.8.14

https://github.com/Laravel-Backpack/CRUD/releases/tag/6.8.14
GitHub commit Patch Available

commit dd25c2086b8e (Laravel-Backpack/CRUD)

Patch available: Laravel-Backpack/CRUD 7.0.41 (contains commit dd25c2086b8e)

https://github.com/Laravel-Backpack/CRUD/commit/dd25c2086b8ea2cb765993b65876c66ab824eef0
GitHub commit Patch Available

commit 76c3a6e50e3f (Laravel-Backpack/CRUD)

Patch available: Laravel-Backpack/CRUD 6.8.15 (contains commit 76c3a6e50e3f)

https://github.com/Laravel-Backpack/CRUD/commit/76c3a6e50e3fbd6d5f633208da5b04acb8322969
GitHub pull request Patch Available

fixes

Patch available: Laravel-Backpack/CRUD 6.8.15 (PR #5994 merged 2026-05-18)

https://github.com/Laravel-Backpack/CRUD/pull/5994
GitHub pull request Patch Available

use scoped query

Patch available: Laravel-Backpack/CRUD 7.0.41 (PR #5991 merged 2026-05-18)

https://github.com/Laravel-Backpack/CRUD/pull/5991
GitHub advisoryMentions a patch (unverified)

CRUD panel query scopes are not enforced on Update, Delete, and Reorder (cross-tenant IDOR) · Advisory · Laravel-Backpack/CRUD · GitHub

https://github.com/Laravel-Backpack/CRUD/security/advisories/GHSA-vgmv-8xjc-6rch

Vendor Advisories for CVE-2026-54180(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Patch Availability(2)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
composerbackpack/crud @ 6.8.14 (fixes >= 6.0.0, < 6.8.14)—ghsa
composerbackpack/crud @ 7.0.38 (fixes >= 7.0.0, < 7.0.38)—ghsa

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(1 across 1 ecosystem)
Packagist(1)
PackageVulnerable rangeFix by version rangeDependents
backpack/crud7.0.0 ... 7.0.9 (38 versions)
  • 6.0.0 up to 6.8.14: fixed in 6.8.14
  • 7.0.0 up to 7.0.38: fixed in 7.0.38
—

Weakness Classification(2)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 10× in last 7d / 47× in last 30d)

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). Most recent first.

  1. 2026-11-01 16:34 UTCEPSS rescoreEPSS 0.5% · 39th percentile
  2. 2026-11-01 07:44 UTCEG score recompute
  3. 2026-11-01 07:44 UTCGHSA enrichmentGHSA-vgmv-8xjc-6rch · GitHub severity HIGH · GitHub CVSS 7.6
  4. 2026-10-31 16:33 UTCEPSS rescoreEPSS 0.5% · 39th percentile
  5. 2026-10-31 00:47 UTCEG score recompute
  6. 2026-10-30 16:34 UTCEPSS rescoreEPSS 0.5% · 39th percentile
  7. 2026-10-29 16:33 UTCEPSS rescoreEPSS 0.5% · 39th percentile
  8. 2026-10-28 16:32 UTCEPSS rescoreEPSS 0.5% · 39th percentile
  9. 2026-10-27 16:32 UTCEPSS rescoreEPSS 0.5% · 39th percentile
  10. 2026-10-26 16:31 UTCEPSS rescoreEPSS 0.5% · 39th percentile
  11. 2026-10-25 16:33 UTCEPSS rescoreEPSS 0.5% · 39th percentile
  12. 2026-10-25 14:19 UTCEG score recompute
  13. 2026-10-24 16:33 UTCEPSS rescoreEPSS 0.5% · 39th percentile
  14. 2026-10-24 04:16 UTCEG score recompute
  15. 2026-10-23 16:32 UTCEPSS rescoreEPSS 0.5% · 39th percentile
  16. 2026-10-22 16:34 UTCEPSS rescoreEPSS 0.5% · 38th percentile
  17. 2026-10-21 16:33 UTCEPSS rescoreEPSS 0.5% · 38th percentile
  18. 2026-10-20 16:33 UTCEPSS rescoreEPSS 0.5% · 38th percentile
  19. 2026-10-19 16:32 UTCEPSS rescoreEPSS 0.5% · 38th percentile
  20. 2026-10-18 16:32 UTCEPSS rescoreEPSS 0.5% · 38th percentile
  21. 2026-10-18 03:31 UTCEG score recompute
  22. 2026-10-17 16:34 UTCEPSS rescoreEPSS 0.5% · 38th percentile
  23. 2026-10-17 07:44 UTCEG score recompute
  24. 2026-10-16 16:42 UTCEPSS rescoreEPSS 0.5% · 38th percentile
  25. 2026-10-15 16:32 UTCEPSS rescoreEPSS 0.5% · 38th percentile
Show 58 more
  1. 2026-10-14 16:33 UTCEPSS rescoreEPSS 0.5% · 38th percentile
  2. 2026-10-13 16:34 UTCEPSS rescoreEPSS 0.5% · 38th percentile
  3. 2026-10-12 16:34 UTCEPSS rescoreEPSS 0.5% · 38th percentile
  4. 2026-10-12 15:56 UTCEG score recompute
  5. 2026-10-11 19:40 UTCEG score recompute
  6. 2026-10-11 16:55 UTCEG score recompute
  7. 2026-10-11 14:18 UTCEG score recompute
  8. 2026-10-11 13:49 UTCEPSS rescoreEPSS 0.5% · 38th percentile
  9. 2026-10-10 20:00 UTCEPSS rescoreEPSS 0.5% · 38th percentile
  10. 2026-10-09 20:07 UTCEPSS rescoreEPSS 0.5% · 38th percentile
  11. 2026-10-09 08:21 UTCEG score recompute
  12. 2026-10-08 17:12 UTCEPSS rescoreEPSS 0.5% · 37th percentile
  13. 2026-10-08 05:15 UTCEG score recompute
  14. 2026-10-07 23:48 UTCEPSS rescoreEPSS 0.5% · 37th percentile
  15. 2026-10-06 19:22 UTCEG score recompute
  16. 2026-10-06 15:18 UTCEPSS rescoreEPSS 0.5% · 37th percentile
  17. 2026-10-06 07:52 UTCEG score recompute
  18. 2026-10-05 17:43 UTCEPSS rescoreEPSS 0.5% · 37th percentile
  19. 2026-10-05 04:58 UTCEG score recompute
  20. 2026-10-04 23:22 UTCEPSS rescoreEPSS 0.5% · 37th percentile
  21. 2026-10-03 16:46 UTCEG score recompute
  22. 2026-10-03 14:26 UTCEPSS rescoreEPSS 0.5% · 37th percentile
  23. 2026-10-02 21:00 UTCEG score recompute
  24. 2026-10-02 17:56 UTCEPSS rescoreEPSS 0.5% · 37th percentile
  25. 2026-10-01 21:28 UTCEG score recompute
  26. 2026-10-01 19:50 UTCEPSS rescoreEPSS 0.5% · 37th percentile
  27. 2026-09-30 18:10 UTCEG score recompute
  28. 2026-09-30 15:03 UTCEPSS rescoreEPSS 0.5% · 37th percentile
  29. 2026-09-30 08:11 UTCEG score recompute
  30. 2026-09-29 15:22 UTCEPSS rescoreEPSS 0.5% · 37th percentile
  31. 2026-09-29 02:13 UTCEG score recompute
  32. 2026-09-28 14:47 UTCEG score recompute
  33. 2026-09-28 13:51 UTCEPSS rescoreEPSS 0.5% · 37th percentile
  34. 2026-09-27 15:55 UTCEG score recompute
  35. 2026-09-27 13:48 UTCEPSS rescoreEPSS 0.5% · 37th percentile
  36. 2026-09-27 02:58 UTCEG score recompute
  37. 2026-09-26 15:59 UTCEPSS rescoreEPSS 0.5% · 37th percentile
  38. 2026-09-24 19:05 UTCEG score recompute
  39. 2026-09-24 14:04 UTCEPSS rescoreEPSS 0.5% · 37th percentile
  40. 2026-09-23 20:03 UTCEG score recompute
  41. 2026-09-23 17:54 UTCEPSS rescoreEPSS 0.3% · 26th percentile
  42. 2026-09-22 19:45 UTCEG score recompute
  43. 2026-09-22 06:42 UTCEG score recompute
  44. 2026-09-20 20:25 UTCEG score recompute
  45. 2026-09-20 20:16 UTCEPSS rescoreEPSS 0.3% · 26th percentile
  46. 2026-09-19 20:29 UTCEG score recompute
  47. 2026-09-18 21:38 UTCEG score recompute
  48. 2026-09-18 19:28 UTCEPSS rescoreEPSS 0.3% · 26th percentile
  49. 2026-09-17 21:19 UTCEG score recompute
  50. 2026-09-17 19:31 UTCEPSS rescoreEPSS 0.3% · 26th percentile
  51. 2026-09-16 19:44 UTCEG score recompute
  52. 2026-09-16 14:08 UTCEPSS rescoreEPSS 0.3% · 26th percentile
  53. 2026-09-16 06:43 UTCEG score recompute
  54. 2026-09-16 05:15 UTCEPSS rescoreEPSS 0.3% · 25th percentile
  55. 2026-09-14 20:27 UTCEG score recompute
  56. 2026-09-14 20:15 UTCEG score recompute
  57. 2026-09-14 18:35 UTCEG score recompute
  58. 2026-08-20 18:42 UTCEG score recomputeFirst assessed: 7.6 HIGH

Related CVEs(same product + same CWE)

Frequently asked(5)

What is CVE-2026-54180?
CVE-2026-54180 is a high-severity vulnerability; its CVE record was published on August 20, 2026. 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…
When was the CVE record for CVE-2026-54180 published?
The CVE record for CVE-2026-54180 was published on August 20, 2026. That is the record's publication date; the vulnerability itself may have been made public earlier. EchelonGraph's copy of the record carries a last-modified date of September 30, 2026; the record at its source may have been updated since.
Is CVE-2026-54180 actively exploited?
CVE-2026-54180 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.5% probability of exploitation in the next 30 days (39th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-54180?
CVE-2026-54180 has a CVSS base score of 7.6 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-54180?
A fix for CVE-2026-54180 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-54180 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-54180

Explore →

Is Your Infrastructure Affected by CVE-2026-54180?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Book a Demo →Browse All CVEs