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

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

Summary

Vulnerability in backpack/crud (CVE-2026-54175). Data can be tampered with by attackers. Exploitable via POST /admin/edit-account-info. Mitigation: upgrade to 7.0.34 or later.

Original description

The description as published by the source.

Summary

The MyAccountController::postAccountInfoForm action bound to POST /admin/edit-account-info calls $this->guard()->user()->update($request->except(['_token'])). Because the controller uses except(['_token']) rather than $request->validated() or the restricted keys defined in AccountInfoRequest::validationData(), any column present in the user model's $fillable array is mass-assigned from the request, including password. Backpack ships a separate POST /admin/change-password route (postChangePasswordForm) that requires old_password verification via ChangePasswordRequest::withValidator. The edit-account-info endpoint silently bypasses that security control.

For the default Laravel 11 App\Models\User model — which Backpack's installer and documentation use as the canonical admin user model — $fillable is ['name','email','password']. The password cast is hashed, so a plaintext password=… form field is automatically hashed and persisted. Any attacker holding an authenticated Backpack session (session theft, stolen cookies, XSS, public-terminal residual session) can permanently take over the account by issuing one POST that includes password=, with no knowledge of the victim's current password. This converts time-limited, session-bound access into persistent account takeover.

Vulnerable code

src/app/Http/Controllers/MyAccountController.php:38

public function postAccountInfoForm(AccountInfoRequest $request)
{
    $…

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-54175 has been found in backpack/crud.
Attackers can target a specific entry point like POST /admin/edit-account-info 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.34 or later.
If unsure, ask your IT team or search "backpack/crud CVE-2026-54175" on the vendor's site.

CVE-2026-54175 (backpack/crud) — CWE-620 / CVSS v3 7.6
Attack vector: remote (network-reachable) / no user interaction
Attack surface: POST /admin/edit-account-info / POST /admin/change-password / password / postChangePasswordForm
Patched: 7.0.34 — 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-620) exists in backpack/crud. Attackers reach the vulnerable code path via POST /admin/edit-account-info.

📍 Affected scope

Check the vendor advisory for the affected versions of backpack/crud. Attack surface: POST /admin/edit-account-info / POST /admin/change-password / password / postChangePasswordForm.

🔥 Severity

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

🔧 How to fix

Update to 7.0.34.

🛡️ 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 POST /admin/edit-account-info requests with malformed payloads or SQL meta-characters. 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
    Hunt for indicators of compromise detect 
    grep 'POST /admin/edit-account-info' /var/log/nginx/access.log | grep -E '(unusual_payload|sqli_pattern)'

    アクセスログで POST /admin/edit-account-info への異常なリクエスト (不正な認証ヘッダ・SQLメタ文字)を過去 30〜90日分捜索。WAF/SIEM があれば該当パスのアラート発火履歴を確認。

  3. 3
    Apply patch patch 
    Upgrade backpack/crud to 7.0.34

    ステージング環境で 7.0.34 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスと、Step 2 で見つけた異常検知の続報チェックを含めること。

  4. 4
    Post-deployment verification verify 
    Replay attack against POST /admin/edit-account-info on staging to confirm patch closes the vector

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

Affected packages

composer backpack/crud
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"7.0.34"}]}]
Packagist backpack/crud
[{"type":"ECOSYSTEM","events":[{"introduced":"7.0.0-alpha.1"},{"fixed":"7.0.34"}]}]

References

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