© 2026 Hedgehog Software, LLC

TwitterGitHubDiscord
More
CommunitiesDocsAboutTermsPrivacy
Search
Star
Setup for Free
FilamentF
Filament•3w ago•
4 replies
Gac

Increased rate or exceptions for vendor methods via livewire/update

3️⃣v3✅ Solved
From looking online and searching here on discord I found one message that mentions:

Livewire apps are being targeted more often now because people are trying to hack them after the recent CVEs that have started to be exploited. You can silence these exceptions in your app's error handler if you want, even in production-only

But recently we noticed an increase in those error getting raised

There are just some of them:

TypeError: Filament\Notifications\Collection::{closure:Filament\Notifications\Collection::fromLivewire():32}(): Argument #1 ($notification) must be of type array, int given
TypeError: Filament\Notifications\Collection::{closure:Filament\Notifications\Collection::fromLivewire():32}(): Argument #1 ($notification) must be of type array, int given


TypeError: Filament\Actions\StaticAction::arguments(): Argument #1 ($arguments) must be of type ?array, int given, called in /home/forge/xxxx/releases/xxxx/vendor/filament/actions/src/Concerns/InteractsWithActions.php on line 359
TypeError: Filament\Actions\StaticAction::arguments(): Argument #1 ($arguments) must be of type ?array, int given, called in /home/forge/xxxx/releases/xxxx/vendor/filament/actions/src/Concerns/InteractsWithActions.php on line 359


Livewire\Features\SupportLockedProperties\CannotUpdateLockedPropertyException: Cannot update locked property: [areFormStateUpdateHooksDisabledForTesting]
Livewire\Features\SupportLockedProperties\CannotUpdateLockedPropertyException: Cannot update locked property: [areFormStateUpdateHooksDisabledForTesting]


TypeError: Filament\Pages\BasePage::getInfolist(): Argument #1 ($name) must be of type string, null given, called in /home/forge/xxx/releases/xxx/vendor/filament/infolists/src/Concerns/InteractsWithInfolists.php on line 270
TypeError: Filament\Pages\BasePage::getInfolist(): Argument #1 ($name) must be of type string, null given, called in /home/forge/xxx/releases/xxx/vendor/filament/infolists/src/Concerns/InteractsWithInfolists.php on line 270


Is there any way to safely block access to
livewire/update
livewire/update
without breaking the app?

In the message I mentioned above there was a link attached ( https://laravel.com/docs/12.x/errors#ignoring-exceptions-by-type ) that lets you ignore certain types of errors, but I don't think that is wise from a security standpoint.

Are there any viable solutions for this?

We are running:
Laravel 12.48.1
Filament v3.3.47
PHP 8.4
Error Handling - Laravel 12.x - The PHP Framework For Web Artisans
Laravel is a PHP web application framework with expressive, elegant syntax. We’ve already laid the foundation — freeing you to create without sweating the small things.
Error Handling - Laravel 12.x - The PHP Framework For Web Artisans
Filament banner
FilamentJoin
A powerful open source UI framework for Laravel • Build and ship admin panels & apps fast with Livewire
20,307Members
Resources
Was this page helpful?

Similar Threads

Recent Announcements

Similar Threads

Livewire\Exceptions\ComponentNotFoundException issue
FilamentFFilament / ❓┊help
3y ago
Livewire Methods on custom fields
FilamentFFilament / ❓┊help
2y ago
The GET method is not supported for route livewire/update. Supported methods: POST.
FilamentFFilament / ❓┊help
12mo ago
The GET method is not supported for route livewire/update. Supported methods: POST.
FilamentFFilament / ❓┊help
3y ago