CVE-2026-54175
HIGHDescription
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.
How to fix
No published remediation has been found for this vulnerability's affected products yet.
Mitigation guidance may be in the linked vendor advisories in the References section below.
TridentStack Control tracks known vulnerabilities across your Windows, macOS, and Linux fleet and shows the fix as soon as one is published. See how it works
CVSS v3 Vector
Exploitability
Impact
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:H/A:L
Exploit Intelligence
Low risk: more likely to be exploited than 32% of all known CVEs.
References
Related Vulnerabilities
Other CWE-620 vulnerabilities, ordered by exploit likelihood. View all
| CVE | Severity | CVSS | EPSS | Exploited | Fix |
|---|---|---|---|---|---|
| CVE-2024-20419 | Critical | 10.0 | 81% | - | Fix |
| CVE-2024-48887 | Critical | 9.8 | 16% | - | Fix |
| CVE-2025-4322 | Critical | 9.8 | 16% | - | - |
| CVE-2024-33699 | Critical | 9.9 | 11% | - | - |
| CVE-2020-7378 | Critical | 9.1 | 2.6% | - | - |
| CVE-2024-12824 | Critical | 9.8 | 2.3% | - | - |
Common questions
How do I fix CVE-2026-54175?
No published fix for CVE-2026-54175 has been found yet. Check the linked vendor advisories for guidance as it becomes available.
Is CVE-2026-54175 being actively exploited?
Not that we know of. CVE-2026-54175 is not in the CISA Known Exploited Vulnerabilities catalog. Its EPSS score of 0.38% is the estimated probability that it will be exploited in the next 30 days. That is higher than 32% of all scored CVEs.
How severe is CVE-2026-54175?
CVE-2026-54175 has a CVSS v3 base score of 7.6, rated high. CVSS rates the technical impact if the vulnerability is exploited, not how likely that is, so weigh it alongside the exploit-prediction score when you decide what to patch first.
Embed a live status badge for CVE-2026-54175
Markdown
[](https://tridentstack.com/cve/CVE-2026-54175)HTML
<a href="https://tridentstack.com/cve/CVE-2026-54175"><img src="https://tridentstack.com/cve/badge/CVE-2026-54175.svg" alt="CVE-2026-54175"></a>Find and fix vulnerabilities across your fleet
TridentStack Control continuously scans your Windows, macOS, and Linux fleet for known vulnerabilities, prioritizes them by severity and active exploitation, and patches them automatically.
This product uses NVD data but is not endorsed or certified by the NVD. EPSS scores courtesy of FIRST.org (https://www.first.org/epss). Source: CISA KEV Catalog. Data as of 2026-09-14.