# CVE-2026-54175: backpack/crud: Unverified password change in MyAccountController via mass assignment

> Authenticated attackers can bypass password verification via mass assignment to change passwords or emails, leading to persistent account takeover.

- **Severity:** High 7.6 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:H/A:L`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 14 Sep 2026
- **Updated:** 14 Sep 2026
- **Also known as:** GHSA-xpv2-hrfc-hw62

## What is CVE-2026-54175?

CVE-2026-54175 is a high-severity vulnerability in Laravel-Backpack CRUD, published on 14 Sep 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official 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.

Weakness: CWE-620 (Unverified Password Change)

## Which versions are affected by CVE-2026-54175?

4 open source packages ship an affected version, including backpack/crud.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `backpack/crud` | Packagist | All versions | 6.8.11 |
| `backpack/crud` | Packagist | All versions | 6.8.11 |
| `backpack/crud` | Packagist | From 7.0.0-alpha.1 | 7.0.34 |
| `backpack/crud` | Packagist | From 7.0.0-alpha.1 | 7.0.34 |

## How do I fix CVE-2026-54175?

Upgrade backpack/crud to a fixed version for your release line: 6.8.11 or 7.0.34.

## Is CVE-2026-54175 being exploited?

There is no known exploitation of CVE-2026-54175 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-54175 and fix it if it is affected.

What it is: CVE-2026-54175 is a high-severity vulnerability in Laravel-Backpack CRUD, published on 14 Sep 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-54175 in the wild and no public exploit code.

Affected packages and fixed versions:
- backpack/crud (Packagist): affected all versions; fixed in 6.8.11
- backpack/crud (Packagist): affected all versions; fixed in 6.8.11
- backpack/crud (Packagist): affected from 7.0.0-alpha.1; fixed in 7.0.34
- backpack/crud (Packagist): affected from 7.0.0-alpha.1; fixed in 7.0.34

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-54175/ (Markdown: https://insights.sbomify.com/CVE-2026-54175/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-54175
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-54175
- OSV: https://osv.dev/vulnerability/CVE-2026-54175

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-54175/
Summaries are generated and may contain mistakes; the official description above is the record.