SEPTEMBER 15, 2026
Live Feed
Back to database
Case File

CVE-2026-54175

HIGH · CVSS 7.6 Public Exploit

Source: NVD + CISA KEV + EPSS · Published 2026-09-14 · Last synced 2026-09-15

CyberRota Analysis

AI-Generated

The vulnerability affects the Backpack CRUD package for Laravel, allowing authenticated users to exploit the MyAccountController to perform mass assignment on sensitive user model attributes, including passwords and authentication columns. This can lead to persistent account takeovers and potential privilege escalation, as attackers can change authentication details without proper validation. Organizations using affected versions should prioritize upgrading to versions 6.8.11 or 7.0.34 to mitigate these risks.

Public Exploit Signal

A public exploit, PoC, GitHub repository or Metasploit reference was detected for this CVE.

Note: these links are listed for security research and verification purposes only.

CVE
CVE-2026-54175
Severity
HIGH
CVSS
7.6
EPSS
N/A

Original NVD Description

backpack/crud provides Create, Read, Update & Delete (CRUD) functions for Backpack, a collection of Laravel packages that help users build custom administration panels. Prior to 6.8.11 and 7.0.34, MyAccountController::postAccountInfoForm in src/app/Http/Controllers/MyAccountController.php at POST /admin/edit-account-info passes request data from $request->except(['_token']) to the user model instead of restricting updates to fields accepted by AccountInfoRequest::validationData(). An attacker with an authenticated Backpack session can therefore mass-assign password, the authentication column, or other deployment-specific fillable attributes. With the default Laravel 11 user model, a submitted plaintext password is automatically hashed and persisted, converting temporary session access into persistent account takeover without the old_password check enforced by the separate password-change route. Changing the authentication email can also enable later password-reset takeover, while additional fillable security attributes can permit deployment-specific privilege escalation or security-control changes. This issue is fixed in versions 6.8.11 and 7.0.34.