GHSA-mhf7-xp6r-6qrc: Livewire: Authorization bypass in #[Authorize] via reordered parameter keys and #[Json] execution order
Impact Three issues allowed actions protected by the #[Authorize] attribute to run against records the current user is not authorized for: 1. Out-of-order parameter keys on actions. #[Authorize] resolved a model parameter by its array key, while the action itself received parameters positionally. A request sending params as an object with reordered integer keys (e.g.
Published Oct 23, 2026
Affected packages
livewire/livewire
- Ecosystem
- Composer (PHP)
- Affected
- >= 4.3.0, < 4.4.8
- Fixed in
- 4.4.8
- Check
composer show livewire/livewire
Advisory details
From the GitHub Advisory Database (CC BY 4.0).
Impact
Three issues allowed actions protected by the #[Authorize] attribute to run against records the current user is not authorized for:
- Out-of-order parameter keys on actions.
#[Authorize]resolved a model parameter by its array key, while the action itself received parameters positionally. A request sending params as an object with reordered integer keys (e.g.{"1": 2, "0": 1}) could pass authorization with a record the user owns while the action received a different record. With#[Authorize('delete', 'comment')]ondeleteComment(Comment $comment), a user could delete another user's comment. - The same issue on event listeners. Methods using both
#[On]and#[Authorize]with a model parameter were affected in the same way through the__dispatchcall. - `#[Json]` methods ran before authorization. When a method had both
#[Json]and#[Authorize], the method body executed before the authorization check. The response was still a 403, but any side effects (such as database writes) had already happened.
Only applications using the #[Authorize] attribute are affected: on methods that take model parameters (issues 1 and 2), or on #[Json] methods (issue 3). Authorization performed inside the method (e.g. $this->authorize(...)) is not affected. Livewire 3.x is not affected.
Patches
Fixed in v4.4.8. Call and event parameters must now be a list or use named (string) keys, otherwise the request is rejected, and #[Json] methods are authorized before they run.
Workarounds
Upgrade to v4.4.8. If you can't upgrade right away, call $this->authorize(...) inside affected methods instead of relying on the #[Authorize] attribute.
Credits
Reported by Yousef Aman (@yousef-aman).
Credited to yousef-aman.
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-81887
Livewire DOM-based cross-site scripting during client-side state handling
medium5.1Sep 2, 2026CVE-2025-54068
Livewire is vulnerable to remote command execution during component property update hydration
critical9.8ExploitedJul 17, 2025CVE-2024-47823
Livewire Remote Code Execution on File Uploads
high7.5Oct 8, 2024GHSA-qwvp-268g-jjm8
Data Leakage Vulnerability in livewire/livewire
mediumMay 15, 2024CVE-2024-21504
Cross-site Scripting in livewire/livewire
medium6.1Mar 19, 2024
