{"items":[{"id":"NVI-00004788","kind":"vulnerability","title":"Livewire: Authorization bypass in #[Authorize] via reordered parameter keys and #[Json] execution order","revision":2,"unknowns":["Customer inventory, deployment, reachability and exploitation have not been inspected."],"lifecycle":"active","identifiers":["GHSA-mhf7-xp6r-6qrc"],"plain_summary":"GitHub lists this reviewed advisory for livewire/livewire. Published version ranges and source prerequisites are shown below; this is not an inspection of a visitor’s application.","review_status":"source_listed","control_topics":[],"public_actions":[{"summary":"Identify the exact component and deployed version, examine the linked publisher’s conditions, and retain evidence of any mitigation.","source_ids":["sr-adac2aa673173cb13292fe202dd39a1f"],"action_type":"investigate","limitations":"Confirm current vendor support, compatibility and deployment evidence. This report has not tested a fix in your system.","current_supported_target":null},{"summary":"The original advisory lists fixed boundaries 4.4.8 for livewire/livewire. Confirm the publisher’s latest guidance.","source_ids":["sr-734ce4e2560ce7fd270b92cc17d1dff3"],"action_type":"vendor_patch","limitations":"Confirm current vendor support, compatibility and deployment evidence. This report has not tested a fix in your system.","current_supported_target":null}],"schema_version":"1.1.0","source_metrics":[{"kind":"CVSS","as_of":"2026-10-23T20:51:30.000Z","value":"6.5 medium","meaning":"GitHub source severity; exploitability and local consequence require separate evidence.","source_id":"sr-adac2aa673173cb13292fe202dd39a1f"}],"why_it_matters":"Published affected context helps an owner decide what evidence to gather. This report has not examined your application.","related_sources":[{"id":"sr-adac2aa673173cb13292fe202dd39a1f","url":"https://github.com/advisories/GHSA-mhf7-xp6r-6qrc","basis":"vendor_advisory","notes":"GitHub Advisory Database; CC-BY-4.0. Each advisory links its original attribution. Null normalizes fields.","title":"GHSA-mhf7-xp6r-6qrc","publisher":"GitHub Advisory Database","observed_at":"2026-10-31T22:07:08.657Z"},{"id":"sr-734ce4e2560ce7fd270b92cc17d1dff3","url":"https://github.com/advisories/GHSA-mhf7-xp6r-6qrc","basis":"vendor_advisory","notes":"GitHub-origin advisory, CC-BY-4.0; OSV is an aggregate copy, not independent corroboration.","title":"GHSA-mhf7-xp6r-6qrc","publisher":"GitHub Advisory Database via OSV","observed_at":"2026-10-31T21:42:30.980Z"}],"affected_context":[{"certainty":"source_listed","source_ids":["sr-adac2aa673173cb13292fe202dd39a1f"],"technology":"livewire/livewire","known_exclusions":[],"conditions_summary":"### Impact\n\nThree issues allowed actions protected by the `#[Authorize]` attribute to run against records the current user is not authorized for:\n\n1. **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.\n2. **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.\n3. **`#[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.\n\nOnly applications using the `#[Authorize]` attribute are affected: on methods that take model parameters (issues 1 and 2), or on `#[Json]` me","public_affected_ranges":[">= 4.3.0, < 4.4.8"]},{"certainty":"source_listed","source_ids":["sr-734ce4e2560ce7fd270b92cc17d1dff3"],"technology":"livewire/livewire","known_exclusions":[],"conditions_summary":"### Impact\n\nThree issues allowed actions protected by the `#[Authorize]` attribute to run against records the current user is not authorized for:\n\n1. **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.\n2. **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.\n3. **`#[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.\n\nOnly applications using the `#[Authorize]` attribute are affected: on methods that take model parameters (issues 1 and 2), or on `#[Json]` me","public_affected_ranges":["ECOSYSTEM: introduced 4.3.0; fixed 4.4.8"]}],"null_published_at":"2026-10-31T22:27:12.375Z","source_updated_at":"2026-10-23T20:51:30.000Z","source_disclosed_at":"2026-10-23T20:51:30.000Z","is_synthetic_fixture":false,"null_last_reviewed_at":null,"public_change_summary":"Source facts changed; compare the preserved prior revision.","null_first_observed_at":"2026-10-31T21:42:30.980Z"},{"id":"NVI-00004788","kind":"vulnerability","title":"Livewire: Authorization bypass in #[Authorize] via reordered parameter keys and #[Json] execution order","revision":1,"unknowns":["Customer inventory, deployment, reachability and exploitation have not been inspected."],"lifecycle":"active","identifiers":["GHSA-mhf7-xp6r-6qrc"],"plain_summary":"OSV carries this publisher advisory for livewire/livewire. This is an aggregated source copy; consult the original publisher and compare update dates.","review_status":"source_listed","control_topics":[],"public_actions":[{"summary":"The original advisory lists fixed boundaries 4.4.8 for livewire/livewire. Confirm the publisher’s latest guidance.","source_ids":["sr-734ce4e2560ce7fd270b92cc17d1dff3"],"action_type":"vendor_patch","limitations":"Confirm current vendor support, compatibility and deployment evidence. This report has not tested a fix in your system.","current_supported_target":null}],"schema_version":"1.1.0","source_metrics":[],"why_it_matters":"Published affected context helps an owner decide what evidence to gather. This report has not examined your application.","related_sources":[{"id":"sr-734ce4e2560ce7fd270b92cc17d1dff3","url":"https://github.com/advisories/GHSA-mhf7-xp6r-6qrc","basis":"vendor_advisory","notes":"GitHub-origin advisory, CC-BY-4.0; OSV is an aggregate copy, not independent corroboration.","title":"GHSA-mhf7-xp6r-6qrc","publisher":"GitHub Advisory Database via OSV","observed_at":"2026-10-31T21:42:30.980Z"}],"affected_context":[{"certainty":"source_listed","source_ids":["sr-734ce4e2560ce7fd270b92cc17d1dff3"],"technology":"livewire/livewire","known_exclusions":[],"conditions_summary":"### Impact\n\nThree issues allowed actions protected by the `#[Authorize]` attribute to run against records the current user is not authorized for:\n\n1. **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.\n2. **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.\n3. **`#[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.\n\nOnly applications using the `#[Authorize]` attribute are affected: on methods that take model parameters (issues 1 and 2), or on `#[Json]` me","public_affected_ranges":["ECOSYSTEM: introduced 4.3.0; fixed 4.4.8"]}],"null_published_at":"2026-10-31T22:12:57.142Z","source_updated_at":"2026-10-23T21:00:04.354Z","source_disclosed_at":"2026-10-23T20:51:30.000Z","is_synthetic_fixture":false,"null_last_reviewed_at":null,"public_change_summary":"First indexed by Null; source disclosure date is shown separately.","null_first_observed_at":"2026-10-31T21:42:30.980Z"}],"next_cursor":null,"snapshot_revision":"42594"}