GHSA-MHF7-XP6R-6QRC

Livewire: Authorization bypass in #[Authorize] via reordered parameter keys and #[Json] execution order

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).

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. {"1": 2, "0": 1}) could pass authorization with a record the user owns while the action received a different record. With #[Authorize('delete', 'comment')] on deleteComment(Comment $comment), a user could delete another user's comment.
2. The same issue on event listeners. Methods using both #[On] and #[Authorize] with a model parameter were affected in the same way through the __dispatch call.
3. #[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.

The application does not correctly enforce access controls, allowing a principal to access resources or operations beyond their granted permissions. Typical impact: unauthorized data access or execution of privileged operations.

GHSA-MHF7-XP6R-6QRC has a CVSS score of 6.5 (Medium). The vector is network-reachable, low privileges required, and no user interaction. A CVSS score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether this affects your application depends on whether the vulnerable code is present and reachable in your environment. A fixed version is available (4.4.8); upgrading removes the vulnerable code path.

Kodem intelligence

Already deployed Kodem?

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.

1. What is GHSA-MHF7-XP6R-6QRC? GHSA-MHF7-XP6R-6QRC is a medium-severity incorrect authorization vulnerability in livewire/livewire (composer), affecting versions >= 4.3.0, < 4.4.8. It is fixed in 4.4.8. The application does not correctly enforce access controls, allowing a principal to access resources or operations beyond their granted permissions.
2. How severe is GHSA-MHF7-XP6R-6QRC? GHSA-MHF7-XP6R-6QRC has a CVSS score of 6.5 (Medium). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.
3. Which versions of livewire/livewire are affected by GHSA-MHF7-XP6R-6QRC? livewire/livewire (composer) versions >= 4.3.0, < 4.4.8 is affected.
4. Is there a fix for GHSA-MHF7-XP6R-6QRC? Yes. GHSA-MHF7-XP6R-6QRC is fixed in 4.4.8. Upgrade to this version or later.
5. Is GHSA-MHF7-XP6R-6QRC exploitable, and should I be worried? Whether GHSA-MHF7-XP6R-6QRC is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
6. What actually determines whether GHSA-MHF7-XP6R-6QRC is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
7. How do I fix GHSA-MHF7-XP6R-6QRC? Upgrade livewire/livewire to 4.4.8 or later.

Other vulnerabilities in livewire/livewire