Repository navigation
Security release: the widget state can no longer be changed by a crafted Livewire request. Upgrading is recommended for every install that uses ActivityTimelineWidget.
Security
- Every public property of
ActivityTimelineWidgetis now#[Locked]. Livewire lets a browser write to any public property that is not locked, so a crafted request could change the source, raise the page size, turn the presentation diagnostics on, or replacepresentationOverrides. Replacing the overrides dropped thehiddenAttributesthe widget was mounted with and revealed those attributes in the change lists. Attributes listed in thehidden_attributesconfiguration were never affected, and the record itself was never swappable, so a timeline always stayed scoped to the record it was mounted with. - The visible window is bounded by the new
pagination.max_per_pagesetting (500 by default). The page size could previously grow without limit, from the "load more" button or from a crafted request. Aper_pageconfigured above the ceiling is still honoured in full. filterByEvent()only accepts an event the timeline offers as a filter tab. The event was already bound as a query parameter, so no injection was possible: the widget simply no longer queries an event it was not configured to expose.
Fixed
- An authorization failure while reading activity is no longer swallowed into the generic error state.
AuthorizationException,AuthenticationException,ValidationException,HttpResponseExceptionand anyHttpExceptionInterfacenow reach the exception handler, so a denied timeline answers with a 403 instead of looking like a record with no history. Any other failure still degrades to the error state and is still reported. - A
per_pageof0or below is clamped to 1.
Upgrading
- No code change is required for a standard setup.
- If you set widget properties from your own JavaScript (
$wire.set(...)), Livewire now throws aCannotUpdateLockedPropertyException. Configure the widget throughmount()or by extendingtimeline()instead. - If you published the configuration file, you can add
'max_per_page' => 500underpagination. Without it, the ceiling falls back to 500. - If one of your custom sources throws an
AuthorizationException, the timeline now answers with a 403 instead of the error panel.
Full changelog: https://github.com/La-boite-a-code/Filament-Activity-Timeline/blob/main/CHANGELOG.md