Summary
Laravel Backpack CRUD: MyAccountController allows changing the login email without a current-password check
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 withChangePasswordRequest, 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
Affected versions
All versions prior to 6.8.14 / 7.0.38.
Fixed versions
- 6.x: 6.8.14
- 7.x: 7.0.38
Impact
The application does not adequately verify the identity of a user, device, or process before granting access. Typical impact: unauthorized access to functions or data reserved for authenticated parties.
CVE-2026-54176 has a CVSS score of 6.5 (Medium). The vector is network-reachable, high privileges required, and no user interaction. A CVSS score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether this affects your application depends on whether the vulnerable code is present and reachable in your environment. A fixed version is available (6.8.14, 7.0.38); upgrading removes the vulnerable code path.
Affected versions
Security releases
Kodem intelligence
Severity tells you how bad this could be in the worst case. It does not tell you whether you are exposed. Exploitability and impact are functions of runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A vulnerable package can sit in your dependency tree and never run.
Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter. Kodem's runtime-powered SCA identifies whether this CVE is reachable in your applications.
Already deployed Kodem?
See it in your environmentNew to Kodem? Get a demo →Remediation advice
Fixed in #5990, the
authentication column is now protected by a current_password check (mirroringChangePasswordRequest) 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 MustVerifyEmail flow.
Frequently Asked Questions
- What is CVE-2026-54176? CVE-2026-54176 is a medium-severity improper authentication vulnerability in backpack/crud (composer), affecting versions >= 6.0.0, < 6.8.14. It is fixed in 6.8.14, 7.0.38. The application does not adequately verify the identity of a user, device, or process before granting access.
- How severe is CVE-2026-54176? CVE-2026-54176 has a CVSS score of 6.5 (Medium). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.
- Which versions of backpack/crud are affected by CVE-2026-54176? backpack/crud (composer) versions >= 6.0.0, < 6.8.14 is affected.
- Is there a fix for CVE-2026-54176? Yes. CVE-2026-54176 is fixed in 6.8.14, 7.0.38. Upgrade to this version or later.
- Is CVE-2026-54176 exploitable, and should I be worried? Whether CVE-2026-54176 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
- What actually determines whether CVE-2026-54176 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
- How do I fix CVE-2026-54176?
- Upgrade
backpack/crudto 6.8.14 or later - Upgrade
backpack/crudto 7.0.38 or later
- Upgrade