CVE-2026-54176: Laravel Backpack CRUD: MyAccountController allows changing the login email without a current-password check
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.
Published Aug 20, 2026
Affected packages
backpack/crud
- Ecosystem
- Composer (PHP)
- Affected
- >= 6.0.0, < 6.8.14
- Fixed in
- 6.8.14
- Check
composer show backpack/crud
backpack/crud
- Ecosystem
- Composer (PHP)
- Affected
- >= 7.0.0, < 7.0.38
- Fixed in
- 7.0.38
- Check
composer show backpack/crud
Advisory details
From the GitHub Advisory Database (CC BY 4.0).
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 MustVerifyEmail flow.
Affected versions
All versions prior to 6.8.14 / 7.0.38.
Fixed versions
- 6.x: 6.8.14
- 7.x: 7.0.38
Credited to pxpm, tabacitu.
References
How this page is made: the data panel comes from the GitHub Advisory Database, CISA’s KEV catalog, the NVD and FIRST EPSS, and updates twice a day. No analysis has been written for this entry yet. Methodology
More Composer (PHP) vulnerabilities
All Composer (PHP) entriesCVE-2026-54175
Laravel Backpack CRUD: Unverified password change in MyAccountController via mass assignment
high7.6Aug 20, 2026CVE-2026-54177
Laravel Backpack CRUD: HasUploadFields keeps the attacker-supplied file extension — public-disk uploads of `shell.php` reach the webserver
medium6.6Aug 20, 2026CVE-2026-54178
Laravel Backpack CRUD: Arbitrary file deletion via attacker-controlled clear_<attr>[] in HasUploadFields::uploadMultipleFilesToDisk
high8.1No fixAug 20, 2026CVE-2026-54179
Laravel Backpack CRUD: SingleBase64Image accepts any base64 payload behind a `data:image` prefix — SVG-with-script lands on the public disk
medium4.4Aug 20, 2026CVE-2026-54180
Laravel Backpack CRUD: CRUD panel query scopes are not enforced on Update, Delete, and Reorder (cross-tenant IDOR)
high7.6Aug 20, 2026CVE-2026-54181
Laravel Backpack CRUD: Stored XSS in the color column — the `@if($column['escaped'])` branches are inverted
medium5.4Aug 20, 2026
