CVE-2026-54176 is a medium-severity (CVSS 6.5) vulnerability in backpack/crud. O3 Security confirms whether CVE-2026-54176 is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.
Laravel Backpack CRUD: MyAccountController allows changing the login email without a current-password check
Real-World Exposure
backpack/crud🐘backpack/crudReal-time download stats are indexed for npm and PyPI packages. This vulnerability affects Packagist packages — download data is not available via public APIs for these ecosystems.
Description
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
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 🐘Packagist | backpack/crud | ≥ 6.0.0&&< 6.8.14 | 6.8.14 |
| 🐘Packagist | backpack/crud | ≥ 7.0.0&&< 7.0.38 | 7.0.38 |
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for backpack/crud. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.
Fix
Update backpack/crud to 6.8.14 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2026-54176 is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
How O3 protects you
O3 pinpoints whether CVE-2026-54176 is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.
Tailored to CVE-2026-54176. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.
Frequently Asked Questions
Is CVE-2026-54176 in your dependencies?
O3 detects CVE-2026-54176 across Packagist dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.