Sign in Sign up
JA · EN · FR
SecPulse
Categories
CVE-2026-54176 medium CVSS 6.5

Authentication Bypass in backpack/crud (CVE-2026-54176)

Summary

Authentication bypass in backpack/crud (CVE-2026-54176). Confidential information can be exposed externally. Exploitable via email. Mitigation: upgrade to 7.0.38 or later.

Original description

The description as published by the source.

Summary

MyAccountController::postAccountInfoForm allows an authenticated user to update
the authentication column (default: email) without verifying their current password.
Because email is the account-recovery anchor, this enables account takeover after
the attacker's session ends: the new email address can be used to request a password
reset from outside the system.

The password-change endpoint in the same controller correctly requires old_password
verification, so the gap is asymmetric.

Details

The postAccountInfoForm action passes $request->validated() directly to
$user->update(). The AccountInfoRequest whitelists the authentication column
(email by default) with no ownership challenge. Contrast this with
ChangePasswordRequest, which uses Hash::check against the stored password before
allowing any change.

Scenarios where this is exploitable include:

  • A brief unauthorized session (e.g. unattended workstation, XSS in the admin panel)
  • An insider/offboarding case where a departing admin sets a personal email address
    before access is revoked, then resets the password after leaving

Patch

Fixed in #5990 — the
authentication column is now protected by a current_password check (mirroring
ChangePasswordRequest) whenever its value changes.

A stronger mitigation — sending a verification link to the new address before
persisting the change — can be layered on top using Laravel's `MustVe…

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-54176 has been found in backpack/crud.
Attackers can target a specific entry point like email over the network to misuse the product.
Confidential information can be exposed externally. CVSS score: 6.5/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-54176" on the vendor's site.

CVE-2026-54176 (backpack/crud) — CWE-287 / CVSS v3 6.5
Attack vector: remote (network-reachable) / no user interaction
Attack surface: email / old_password / postAccountInfoForm / AccountInfoRequest
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

Authentication bypass (CWE-287) exists in backpack/crud. Attackers reach the vulnerable code path via email.

📍 Affected scope

Check the vendor advisory for the affected versions of backpack/crud. Attack surface: email / old_password / postAccountInfoForm / AccountInfoRequest.

🔥 Severity

Severity: Medium (CVSS 6.5/10). Confidential information can be exposed externally.

🔧 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