Sign in Sign up
JA · EN · FR
SecPulse
Categories
CVE-2026-54180 high CVSS 7.6

Vulnerability in backpack/crud (CVE-2026-54180)

Summary

Vulnerability in backpack/crud (CVE-2026-54180). Data can be tampered with by attackers. Exploitable via addBaseClause. Mitigation: upgrade to 7.0.38 or later.

Original description

The description as published by the source.

Summary

Backpack CRUD's list and read operations correctly apply any query scopes
registered via addClause() / addBaseClause() (e.g. tenant isolation, user
ownership). However, the Update, Delete, and Reorder operations
bypassed these scopes, fetching records directly from the unscoped model query.

An authenticated user who knows or can guess a record's primary key could
therefore update, delete, or reorder records that should be invisible to them —
a classic IDOR on write paths.

Applications that rely on addBaseClause for row-level access control
(multi-tenancy, per-user data isolation) are affected.

Impact

Any Backpack CRUD panel that uses addBaseClause or addClause to restrict
which rows a user may access is affected on its write operations.
An authenticated low-privilege user can modify or delete records belonging to
other tenants / users.

Patches

Apply the fixed release for your major version:

  • v6: upgrade to 6.8.14 or later
  • v7: upgrade to 7.0.38 or later

The fix ensures Update, Delete, and Reorder all resolve records through the same
scoped query used by the read side.

Workarounds

If you cannot upgrade immediately, add explicit Gate / Policy checks in your
CrudController's update(), destroy(), and reorder() methods to verify
the authenticated user is permitted to act on the resolved record.

Credits

Reported by Vishal Shukla (@shukla304).

Source: GitHub Security Advisories (Global) NVD GitHub Advisory

Auto-generated summary

Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.

A vulnerability tracked as CVE-2026-54180 has been found in backpack/crud.
Attackers can target a specific entry point like addBaseClause over the network to misuse the product.
Data can be tampered with by attackers. CVSS score: 7.6/10.
What to do: upgrade backpack/crud to 7.0.38 or later.
If unsure, ask your IT team or search "backpack/crud CVE-2026-54180" on the vendor's site.

CVE-2026-54180 (backpack/crud) — CWE-639 / CVSS v3 7.6
Attack vector: remote (network-reachable) / no user interaction
Attack surface: addBaseClause / addClause / Gate / Policy
Patched: 7.0.38 — apply immediately
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.

❓ What is the problem

A vulnerability (CWE-639) exists in backpack/crud. Attackers reach the vulnerable code path via addBaseClause.

📍 Affected scope

Check the vendor advisory for the affected versions of backpack/crud. Attack surface: addBaseClause / addClause / Gate / Policy.

🔥 Severity

Severity: High (CVSS 7.6/10). Data can be tampered with by attackers.

🔧 How to fix

Update to 7.0.38.

🛡️ Workaround

Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.

🔍 Detection

Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r 'backpack/crud' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.

Response actions

Concrete steps and command examples for SOC/SRE teams to execute in order

  1. 1
    Identify exposure identify 
    grep -r 'backpack/crud' . | grep -v node_modules

    リポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で backpack/crud を grep し、稼働しているサービス・バージョンを把握する。

  2. 2
    Apply patch patch 
    Upgrade backpack/crud to 7.0.38

    ステージング環境で 7.0.38 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。

  3. 3
    Post-deployment verification verify 
    Confirm patched version is live in production

    パッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。

Affected packages

composer backpack/crud
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"7.0.38"}]}]
Packagist backpack/crud
[{"type":"ECOSYSTEM","events":[{"introduced":"7.0.0"},{"fixed":"7.0.38"}]}]

References

We use cookies for analytics and ad measurement. This setting applies to all Game co., Ltd. sites. Details