NewYour coding agent can read the release notes before it upgrades.Set up the MCP server →
Packagist
Packagist, #4730 most downloaded on Packagist
A media picker and manager for Filament, with Glide-backed image transformations and per-image curations.
Latest stable
v5.6.2
Last release 18 days ago
04 Nov 2026
Ships fairly regularly
a new release about every 2 weeks
Nearly every release is documented
notes for 60 of the last 60 stable releases
Nothing withdrawn
no release was ever pulled
5 years old
285 releases · first in 2022
Drag across the ruler to compare, or tap a release to open it.
chore(deps): bump actions/setup-node from 7.0.0 to 7.1.0 in the github-actions group by @dependabot[bot] in https://github.com/awcodes/filament-curato
Full Changelog: https://github.com/awcodes/filament-curator/compare/v5.6.1...v5.6.2
This release fixes reading images uploaded to a cloud temporary disk, which failed with Unable to decode input. when Livewire's temporary uploads are
This release fixes reading images uploaded to a cloud temporary disk, which failed with Unable to decode input. when Livewire's temporary uploads are stored on S3 or GCS.
root to a path that already included it, so a disk with a custom root looked for public/public/livewire-tmp/....Thanks to @rojtjo for the fix.
5.x: Fix double root issue by @rojtjo in https://github.com/awcodes/filament-curator/pull/780Full Changelog: https://github.com/awcodes/filament-curator/compare/v5.6.0...v5.6.1
Your coding agent can read these notes before it upgrades. Set up the MCP server →
The rich editor integration can store media ids again, with a file attachment provider that reads them.
The rich editor integration can store media ids again, with a file attachment provider that reads them.
AttachCuratorMediaPlugin::make()->storeMediaIds() inserts library media with its key in the image's data-id, the attribute Filament uses for its own attachments. It's off by default; without it, inserted media stays a plain image as in 5.5. (#779)CuratorFileAttachmentProvider, which the plugin supplies when it stores media ids. It resolves each key to the media's current URL whenever the content is edited or rendered, so images follow replaced files and moved disks.
disk(), directory(), acceptedFileTypes() and maxSize().Uploader::storeUploadedFile() and Uploader::isAcceptedFile() are now public.Filament reads a provider from plugins only on a model's rich content attribute and in RichContentRenderer. An editor outside both, such as one in a nested form, needs the provider set on the field. See the rich editor docs.
Content saved before 5.5 with data-id attributes renders correctly again once storeMediaIds() is on.
Full Changelog: https://github.com/awcodes/filament-curator/compare/v5.5.5...v5.6.0
This release fixes the picker modal, which failed to open on every CuratorPicker in v5.5.3 and v5.5.4 with Property type not supported in Livewire for
This release fixes the picker modal, which failed to open on every CuratorPicker in v5.5.3 and v5.5.4 with Property type not supported in Livewire for property: [{}]. Upgrading is recommended for every install on v5.5.3 or v5.5.4.
Rule::dimensions(), are passed as that string and still apply to uploads.Fixed in #777.
Full Changelog: https://github.com/awcodes/filament-curator/compare/v5.5.4...v5.5.5
This release allows enshrined/svg-sanitize 1.0, which fixes GHSA-9rjx-3jch-6vjf, GHSA-m9xh-6747-9r6f and GHSA-v383-3rw5-q8rf. Upgrading is recommended
This release allows enshrined/svg-sanitize 1.0, which fixes GHSA-9rjx-3jch-6vjf, GHSA-m9xh-6747-9r6f and GHSA-v383-3rw5-q8rf. Upgrading is recommended for every 5.x install. Composer now refuses to install 0.22.0 by default, so without this release composer update is blocked in apps using Curator.
enshrined/svg-sanitize constraint widened to ^0.22|^1.0.
@import and url() references inside an SVG's <style> are now stripped.xmlns="&ns_svg;".curator:sanitize-svgs skips stored SVGs it can't sanitize and leaves them unchanged.Added in #772.
Full Changelog: https://github.com/awcodes/filament-curator/compare/v5.5.3...v5.5.4
This release contains security fixes. Upgrading is recommended for every 5.x install. Details will be published in security advisories.
This release contains security fixes. Upgrading is recommended for every 5.x install. Details will be published in security advisories.
storage/app/.cache by default) and any CDN in front of your media.php artisan curator:repair-extensions --dry-runphp artisan curator:repair-extensionsthumbnail_url, medium_url, large_url, <x-curator-glider> and the table column, for media that isn't public.curator.temporary_url_expiration (minutes, default 5), which url also uses.<x-curator-glider> given a plain path returns 404, so pass the record or its id.limitToDirectory() folder and subfolders;update ability.
curator.curation_max_dimension (default 8192).Added in #763, #764 and #765.
Full Changelog: https://github.com/awcodes/filament-curator/compare/v5.5.2...v5.5.3
This release contains security fixes. Upgrading is recommended for every 5.x install, including installs already on 5.5.1. Details will be published i…
This release contains security fixes. Upgrading is recommended for every 5.x install, including installs already on 5.5.1. Details will be published in security advisories.
If you're upgrading from 5.5.0 or earlier, also follow the 5.5.1 upgrade step and run php artisan curator:repair-extensions --dry-run, then php artisan curator:repair-extensions.
application/octet-stream, are accepted only when listed exactly.text/* or application/* no longer matches them.UploadedFile::fake()->create() files are zero-filled, so they're now detected as application/octet-stream and rejected..doc, .xls and .ppt files keep their type..csv and .ics files detected as plain text are typed text/csv and text/calendar.curator:repair-extensions only deletes an original after its replacement has been written.mimetypes validation message is used again.Added in #755.
Full Changelog: https://github.com/awcodes/filament-curator/compare/v5.5.1...v5.5.2
This release contains security fixes. Upgrading is recommended for every 5.x install. Details will be published in security advisories.
This release contains security fixes. Upgrading is recommended for every 5.x install. Details will be published in security advisories.
Check existing media for files stored under an unsafe extension, then repair them:
php artisan curator:repair-extensions --dry-run # report only
php artisan curator:repair-extensions
old -> new, so keep the output..JPG and harmless mismatches are reported but not renamed. Nothing is deleted.See File types.
$wire.set('diskName', …)) now throws CannotUpdateLockedPropertyException.settings..jpeg stays .jpeg..txt for plain text with an uncommon extension, and .bin for application/octet-stream.view ability, as the panel's download already did.base_url. Existing image URLs are unchanged.curator/ by default) is now served correctly.CuratorPanel::setMediaForm() method.Added in #752, #753 and #754.
Filament 4 users are covered: 5.x serves both majors. Fixes for the 4.x and 3.x lines will follow.
Full Changelog: https://github.com/awcodes/filament-curator/compare/v5.5.0...v5.5.1
A correctness release from an audit of 5.x: rendering, the picker, the media observer, the cropper and the docs. It's a minor release because two beha
A correctness release from an audit of 5.x: rendering, the picker, the media observer, the cropper and the docs. It's a minor release because two behaviours change. Read Changed before upgrading.
CuratorPicker now uses its own setting first, then the facade's, then config. That covers disk, directory, visibility, acceptedFileTypes, minSize, maxSize and the image-resize options. If you configure the facade, for example Curator::disk('s3'), your pickers now use that setting unless they set their own. See Global upload defaults.Curator, Glide or Curation in a service provider's register() or boot() used to be lost after the first job or request. It now lasts. Settings changed during a request or job are still reset for the next one.curation_formats are the ones the cropper can save. bmp, gif and svg were offered by default but always failed to save. Published configs that still list them are filtered.src when rendered with RichContentRenderer. Content saved by earlier versions still carries a data-id. Rendering saved content has a one-off cleanup.2x) requested a 2px-wide image.rules() never reached the uploader. Per-file rules such as dimensions: and mimes: now apply to uploads.maxWidth() threw for any Width value.curator:install: UUID and tenancy installs kept the base model, and the tenancy option wrote invalid PHP.<x-curator-curation>: it threw for UUID or ULID keys and when curation was omitted.resource.pages.*, resource.schemas.form and resource.tables.table were ignored.urlProvider(): passing an instance threw.CuratorColumn::resolution(): it had no effect. It now requests the image at the display size times the resolution.<x-filament-actions::modals />.curator:upgrade: it was never registered and targeted v2 → v3.Added in #744–#751.
Filament 4 users are covered: 5.x serves both majors.
Full Changelog: https://github.com/awcodes/filament-curator/compare/v5.4.0...v5.5.0
One hook for every action that deletes media. Curator::configureDeleteActionsUsing() configures the resource table's row and bulk delete actions, the
One hook for every action that deletes media. Curator::configureDeleteActionsUsing() configures the resource table's row and bulk delete actions, the edit page's delete action, and the picker panel's delete action. Use it to add a warning or a guard without a global DeleteAction::configureUsing(). Call it from a service provider's boot() method:
use Awcodes\Curator\Facades\Curator;
use Awcodes\Curator\Models\Media;
use Filament\Actions\Action;
Curator::configureDeleteActionsUsing(function (Action $action): void {
$action->modalDescription(fn (?Media $record) => "Delete {$record?->name}? It may still be in use.");
});
The callback receives the Filament action, so any action method works, including before() with $action->halt(). Single-record actions receive the media as $record and the bulk action receives $records. Type $record as nullable: the picker panel only resolves it once the delete dialog opens, and not at all if the user may not delete that item. If you have replaced the resource's page or table classes, pass your delete actions through Curator::configureDeleteAction() to pick up the hook. See Customising delete actions.
deleteAny(). If your policy restricted delete() on individual records but didn't define deleteAny(), bulk delete from the media table removed records the policy denies. Each selected record is now checked. Records the user may not delete are skipped, and Filament reports a partial delete.Added in #739, with tests for each delete path.
Filament 4 users are covered: 5.x serves both majors.
Deleting a media item no longer breaks every page that renders it. threw Invalid media item provided to Glider component. whenever an id no longer res
<x-curator-glider> threw Invalid media item provided to Glider component. whenever an id no longer resolved and no fallback was set, so pages returned a 500. It now renders nothing and logs a warning naming the missing id. Misconfiguration still throws, now with a clearer message: a fallback name that was never registered reports The [name] glider fallback is not registered., and a fallback without a source still throws as before.
:media="null" without a fallback now renders nothing instead of throwing.width and height attributes now match the image Glide serves. Asking for width="960" on a 1600×900 image wrote height="900" while Glide returned 960×540. That distorted the box and shifted the layout. The missing side is now derived from the aspect ratio, in either direction. A srcset on a path or fallback with unknown dimensions no longer divides by zero.curator.default_directory is null), the observer called deleteDirectory(null) once the disk held no files, which removed the disk root along with any empty folders. Renaming or replacing root-level media also stored paths with a leading slash (/renamed.jpg), which the Glide route then couldn't find. Both are fixed.storage/app/public. Media on any other disk stored without error and then returned a 500. That included a fresh Laravel app's local disk, which default_disk follows through FILESYSTEM_DISK, as well as S3 and MinIO. Glide now reads each item from the disk it was stored on, so cloud disks no longer need a custom server config. A config passed to Glide::serverConfig() is still used exactly as given.curator.default_directory. With it set, new files landed in that directory while the picker and rich editor panels opened at the disk root, so a file you had just uploaded wasn't listed. The picker, rich editor, media form, bulk upload and CuratorUtils now all fall back to it.Fixed in #738, with regression tests for each fix.
Filament 4 users are covered: 5.x serves both majors.
Several Curator pickers bound to the same MorphMany relationship no longer clobber or duplicate each other's rows.
MorphMany relationship no longer clobber or duplicate each other's rows.A form with more than one picker on a single relationship — featured, thumb, gallery, told apart by typeValue() — gained a row on every save, and the pickers displayed images belonging to their siblings.
The MorphMany save path reads and writes its rows in five places. Three of them disagreed about which rows belong to the picker doing the work:
featured picker rewrote the type of every row sharing that media_id — including the thumb row. The orphaned picker then found nothing of its own and created a replacement. One extra row per save, forever. Introduced in v5.0.6 by the sort-order fix: before that the update matched nothing at all, which was the sort-order bug itself.typeValue() loaded every row on the relationship — including rows owned by typed siblings — and then wrote them back as untyped copies of itself. Present since v5.0.0.->typeValue('0') — a backed enum whose first case is zero, for instance — stored a row that no later lookup could match, and every save appended another duplicate. Present since v5.0.0.All five now scope identically. A null type value matches on type IS NULL, which is what the existing lookup and delete already relied on.
Reported in #734, fixed in #735 (thanks @appdezign) and #736. Four regression tests cover it.
Filament 4 users are covered — 5.x serves both majors.
The RichEditor integration now closes the Curator panel it opened, instead of whichever modal happens to come first on the page.
Curator closed its media panel by searching the whole document for the first .fi-modal and clicking that element's close control. Filament renders every mounted action modal as a sibling in stack order, so the first match is the outermost modal — not the panel the selection was made in.
On an ordinary page form the panel is the only modal on screen, so that lookup happened to be right and the bug stayed hidden. Nest the editor inside another modal — a Mason brick, a relation manager edit action, a RichContentCustomBlock — and inserting an image closed the host modal instead, discarding the unsaved form. In Mason's case the brick was silently never added.
Livewire dispatches from the component's own root element, so the insert event already identifies which panel sent it. Curator now walks up from there to its enclosing modal and closes that one by id, through Filament's own close-modal event.
Reported as awcodes/mason#53. Present since the RichEditor integration shipped in v4.0.0; this is not a regression of the context scoping added in v5.0.3, which addressed a different problem in the same handler.
Filament 4 users are covered — 5.x serves both majors.
Removed the unused third parameter from CuratorPicker::relationship().
CuratorPicker::relationship().The signature carried ?Closure $callback = null from the first commit that added relationship support, copied from Filament's Select::relationship() where the equivalent argument is $modifyQueryUsing. It was never referenced in the method body, so anything passed to it was silently discarded — worse than not offering it, since the call reads as though it does something.
No caller breaks: nothing in the package, its tests or its docs ever passed a third argument, and PHP accepts extra arguments to userland functions without error.
Dropped the Pint mb_str_functions rule and reverted the mb_ltrim() it had introduced in the Uploader form component.
mb_str_functions rule and reverted the mb_ltrim() it had introduced in the Uploader form component.mb_ltrim() is a PHP 8.4 function, and this package declares ^8.2. Below 8.4 it resolves only through symfony/polyfill-mbstring, which is not required directly, so a lock file resolving an older polyfill on PHP 8.2 or 8.3 could fatal with Call to undefined function mb_ltrim(). Affects v5.3.2.
docs/ directory.Fixes an SVG sanitization bypass and unvalidated curation paths. See GHSA-3xm3-q2fj-x8rq for the full advisory.
Fixes an SVG sanitization bypass and unvalidated curation paths. See GHSA-3xm3-q2fj-x8rq for the full advisory.
payload.txt was stored unsanitized. Sanitizing now keys off the detected type as well as the extension, in both the uploader and CuratorUtils::importMedia, and the serving layer pins Content-Type from the stored extension instead of the sniffed bytes.saveCuration() consumed the crop payload unvalidated, so a key such as ../../other could overwrite a sibling file inside the storage disk. The payload is now validated before anything is written.curator:sanitize-svgs now selects on the detected type as well as the extension, so rows stored under a spoofed filename are no longer invisible to it.Re-scan stored media to clean up anything already on disk:
php artisan curator:sanitize-svgs --dry-run # report only
php artisan curator:sanitize-svgs
The serving-layer change already prevents affected rows from rendering as documents, so this is cleanup rather than the primary fix.
exif form view. It was not referenced anywhere in the package and could not render as shipped, since it requested an Alpine component that is never registered. If you published views with vendor:publish --tag=curator-views, your local copy is untouched by this removal and still contains a raw {!! !!} echo of EXIF metadata — escape or delete it.Reported by Afsana Alijabarova (@afa114).
fix: align Media docblock with the nullable migration columns by @awcodes in https://github.com/awcodes/filament-curator/pull/722
Full Changelog: https://github.com/awcodes/filament-curator/compare/v5.3.0...v5.3.1
Support Filament 4 and 5 from a single branch by @awcodes in https://github.com/awcodes/filament-curator/pull/720
Full Changelog: https://github.com/awcodes/filament-curator/compare/v5.2.0...v5.3.0
The media picker's search now matches each term on its own instead of looking for the whole input as a single substring. A file named my-image.png cou
The media picker's search now matches each term on its own instead of looking for the whole input as a single substring. A file named my-image.png could not previously be found by typing "my image".
The search is split on whitespace, hyphens and underscores, and every term has to match — though any of the five searchable columns (name, title, alt, caption, description) may be the one matching it. So my-image.png is now found by "my image", "my_image", "my-image", or "image my", while my-document.png stays out of those results.
LIKE wildcards typed into the search are now escaped, so searching for 100% looks for a literal percent sign rather than matching everything. Worth knowing that _ has always been an unescaped single-character wildcard, so photo_8-sunset matched photo-8-sunset by accident while a hyphen did nothing; that inconsistency is gone.
Case sensitivity is still left to the database — Postgres LIKE is case-sensitive where MySQL and SQLite are not. That is unchanged from previous versions.
Thanks to @amywestlake for reporting this and proposing the original approach in #623.
Search results are now ordered by the panel's sort direction, matching the unfiltered list. There was no ORDER BY at all before, so the 50-row limit truncated an arbitrary slice of matches.
GliderFallback's setters were typed to require a value, while every property except the name is optional and every getter already returned null. Building a fallback from a conditional expression — the usual reason to have one — threw a TypeError in a service provider before the application could boot:
GliderFallback::make('logo')
->alt(config('app.name'))
->source(filled(setting('logo')) ? $logo->url : Vite::image('logo.webp'))
alt(), height(), source(), type() and width() now all accept null.
A registered fallback that ends up with no source still cannot be rendered, but it now names itself — The [logo] glider fallback does not have a source. — instead of reporting the media item as invalid, which pointed at the wrong thing.
Thanks again to @battulga0719 for reporting this in #718.
No changes are required for ordinary use. Two notes:
GliderFallback and overrode any of the setters with the narrower string/int signature, widen it to ?string/?int to match the parent.0 into the picker search previously reset the list to show everything. It now searches for "0"; whitespace-only input is what falls back to the unfiltered list.Applications that already set acceptedFileTypes() themselves — globally or per field — were never affected, because the vulnerable list was only used…
Curator's upload components fell back to a default list of accepted file types that included text/html, application/xhtml+xml, text/javascript, application/xml and application/octet-stream. An authenticated user with permission to upload media could upload an HTML file containing a <script> tag. The file was stored unmodified and later served from the application's own origin, executing the script with the session of whoever opened it.
This affected the Media resource form, MultiUploadAction, CuratorPicker and the rich editor's attachment flow, which all share the same default. Applications that already set acceptedFileTypes() themselves — globally or per field — were never affected, because the vulnerable list was only used as a fallback.
The default is now MimeType::defaults(): the full list minus types that are effectively executable content. MimeType::toArray() is unchanged, so code referencing the enum directly still works. As defense in depth, media served through Curator's own route now sends X-Content-Type-Options: nosniff, and restricted types are forced to Content-Disposition: attachment.
If your application genuinely needs to host these types, opt back in explicitly:
use Awcodes\Curator\Enums\MimeType;
Curator::acceptedFileTypes([...MimeType::defaults(), 'text/html']);
Note that Curator only sanitizes SVG uploads. Anything else you allow is stored and served verbatim, and with the default public disk it is also reachable through the storage symlink, where the new response headers do not apply. Serve deliberately-allowed executable types from a private disk.
The 3.x line is not affected — its accepted types come from config('curator.accepted_file_types'), whose default has always been limited to images and PDFs.
Glider fallbacks could not be used at all. Several faults compounded:
GliderFallback::make() passed the name through the container, but the class has no constructor, so Laravel discarded it. The name stayed null and getName() threw a TypeError, meaning a fallback built exactly as documented failed before it could be registered.<x-curator-glider> component rejected a null media item, which is the main reason to configure a fallback in the first place. It now accepts null.handleInt() checked the raw id rather than the looked-up record, so the fallback branch never ran and a missing record produced "Attempt to read property path on null" instead. The documented <x-curator-glider :media="1" fallback="thumbnail"/> could not work.Fallback resolution now happens in one place, so a null media item, an id that does not resolve, and a blank string all reach it. An unregistered fallback name, or one with no source, no longer dereferences null.
Also fixed while in there:
GliderFallback's optional getters were typed non-nullable while every property defaults to null, so a partially configured fallback threw. They are nullable now.GliderFallback::isPreviewable() called Curator::isResizable(), reporting svg sources as not previewable.Thanks to @battulga0719 for reporting the fallback issues in #717.
The media picker breadcrumb's root Disk label and the Selected Files heading in the selection modal were hardcoded in English and ignored the active l
curator::views.details.disk key, so it is already translated in every shipped locale.Adds a new attach_curator_media.modal.selected_files key under resources/lang/en/views.php. Other locales fall back to English until translated — contributions welcome.
Thanks to @Elgorm for reporting and fixing this in #716.
Fixes a broken access control vulnerability (CWE-862 / CWE-639, CVSS 7.6 High): the media picker modal's per-item Edit, Delete, and Download actions r…
Fixes a broken access control vulnerability (CWE-862 / CWE-639, CVSS 7.6 High): the media picker modal's per-item Edit, Delete, and Download actions resolved their target Media record from client-supplied input without a per-record authorization check or tenant scoping. Any authenticated user able to reach a form containing a CuratorPicker field could edit, delete, or download arbitrary Media records by id — bypassing any MediaPolicy the host app defines and Curator's own multi-tenancy scoping. The Download action also streamed a client-supplied disk/path directly.
These actions now enforce the resource's authorization policy per-record and apply the same tenant scoping used elsewhere in the picker, and Download streams from the stored record instead of the request payload. No configuration changes are required after upgrading.
See the security advisory for full details: https://github.com/awcodes/filament-curator/security/advisories/GHSA-3m5g-3j68-ghvp
Fixes a stored XSS vulnerability (CWE-79, CVSS 5.4 Moderate): SVG files uploaded through the Curator panel were served inline without sanitization, al…
Fixes a stored XSS vulnerability (CWE-79, CVSS 5.4 Moderate): SVG files uploaded through the Curator panel were served inline without sanitization, allowing embedded JavaScript to execute in the application's origin when a user opened the file via the View action. SVG uploads are now sanitized (scripts, event handlers, and remote references stripped) before being written to storage.
After upgrading, run php artisan curator:sanitize-svgs to clean any SVGs uploaded before
this release (use --dry-run to preview first).
See the security advisory for full details: https://github.com/awcodes/filament-curator/security/advisories/GHSA-8vm9-f75m-5h2m
enshrined/svg-sanitize as a dependency.Fixes a cross-tenant media metadata disclosure in the Curator picker search. In multitenant panels, an authenticated user could retrieve other tenants
Fixes a cross-tenant media metadata disclosure in the Curator picker search. In multitenant panels, an authenticated user could retrieve other tenants' media metadata by typing in the picker search box. Single-tenant installs are not affected.
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:L/I:N/A:N)Upgrade recommended for any multitenant deployment. Also fixed in 3.7.8 and 4.1.1. A GitHub Security Advisory and CVE will be linked here once published.
Full Changelog: https://github.com/awcodes/filament-curator/compare/v5.1.0...v5.1.1
Chore(deps): Bump actions/checkout from 6 to 7 by @dependabot[bot] in https://github.com/awcodes/filament-curator/pull/705
Full Changelog: https://github.com/awcodes/filament-curator/compare/v5.0.8...v5.1.0
Chore(deps): Bump dependabot/fetch-metadata from 3.0.0 to 3.1.0 by @dependabot[bot] in https://github.com/awcodes/filament-curator/pull/699
Full Changelog: https://github.com/awcodes/filament-curator/compare/v5.0.7...v5.0.8
Chore(deps): Bump dependabot/fetch-metadata from 2.5.0 to 3.0.0 by @dependabot[bot] in https://github.com/awcodes/filament-curator/pull/691
Full Changelog: https://github.com/awcodes/filament-curator/compare/v5.0.6...v5.0.7
Chore: improved test suite by @awcodes in https://github.com/awcodes/filament-curator/pull/684
Full Changelog: https://github.com/awcodes/filament-curator/compare/v5.0.5...v5.0.6
Fix: getVisibility() ignores config('curator.default_visibility') by @awcodes in https://github.com/awcodes/filament-curator/pull/682
Full Changelog: https://github.com/awcodes/filament-curator/compare/v5.0.4...v5.0.5
Fix: version conflicts from 4.x merge
Full Changelog: https://github.com/awcodes/filament-curator/compare/v5.0.3...v5.0.4
Fix: glide server config in GlideManager and update upgrade guide by @awcodes in https://github.com/awcodes/filament-curator/pull/673
Full Changelog: https://github.com/awcodes/filament-curator/compare/v5.0.2...v5.0.3
Fix: glide server config in GlideManager and update upgrade guide
Full Changelog: https://github.com/awcodes/filament-curator/compare/v5.0.1...v5.0.2
Fix: Use Curator facade to determine isResizable/isPreviewable by @adicacan in https://github.com/awcodes/filament-curator/pull/663
Full Changelog: https://github.com/awcodes/filament-curator/compare/v5.0.0...v5.0.1
## What's Changed * Filament v5 support Full Changelog: https://github.com/awcodes/filament-curator/compare/v4.0.0...v5.0.0
Full Changelog: https://github.com/awcodes/filament-curator/compare/v4.0.0...v5.0.0
Add missing Czech translations by @kojdad-alt in https://github.com/awcodes/filament-curator/pull/784
Full Changelog: https://github.com/awcodes/filament-curator/compare/v4.2.6...v4.2.7
This release fixes reading images uploaded to a cloud temporary disk, which failed with Unable to decode input. when Livewire's temporary uploads are
This release fixes reading images uploaded to a cloud temporary disk, which failed with Unable to decode input. when Livewire's temporary uploads are stored on S3 or GCS.
root to a path that already included it, so a disk with a custom root looked for public/public/livewire-tmp/....Thanks to @rojtjo for the fix.
4.x: Fix double root issue by @rojtjo in https://github.com/awcodes/filament-curator/pull/781Full Changelog: https://github.com/awcodes/filament-curator/compare/v4.2.5...v4.2.6
This release fixes the picker modal, which failed to open on every CuratorPicker in v4.2.3 and v4.2.4 with Property type not supported in Livewire for
This release fixes the picker modal, which failed to open on every CuratorPicker in v4.2.3 and v4.2.4 with Property type not supported in Livewire for property: [{}]. Upgrading is recommended for every install on v4.2.3 or v4.2.4.
Rule::dimensions(), are passed as that string and still apply to uploads.Fixed in #778 (backport of #777).
Full Changelog: https://github.com/awcodes/filament-curator/compare/v4.2.4...v4.2.5
This release allows enshrined/svg-sanitize 1.0, which fixes GHSA-9rjx-3jch-6vjf, GHSA-m9xh-6747-9r6f and GHSA-v383-3rw5-q8rf. Upgrading is recommended
This release allows enshrined/svg-sanitize 1.0, which fixes GHSA-9rjx-3jch-6vjf, GHSA-m9xh-6747-9r6f and GHSA-v383-3rw5-q8rf. Upgrading is recommended for every 4.x install. Composer now refuses to install 0.22.0 by default, so without this release composer update is blocked in apps using Curator.
enshrined/svg-sanitize constraint widened to ^0.22|^1.0.
@import and url() references inside an SVG's <style> are now stripped.xmlns="&ns_svg;".curator:sanitize-svgs skips stored SVGs it can't sanitize and leaves them unchanged.Added in #774 (backport of #772).
Full Changelog: https://github.com/awcodes/filament-curator/compare/v4.2.3...v4.2.4
This release contains security fixes for the 4.x line. Upgrading is recommended for every 4.x install. Details will be published in security advisorie…
This release contains security fixes for the 4.x line. Upgrading is recommended for every 4.x install. Details will be published in security advisories.
Purge Glide's cache (storage/app/.cache by default) and any CDN in front of your media.
thumbnail_url, medium_url, large_url) and the Glider for media that isn't public carry a signed expiry. They're served with private cache headers.curator.temporary_url_expiration config (minutes, default 5).limitToDirectory(), and for the current tenant.update ability.
curator.curation_max_dimension (default 8192).Added in #766, #767 and #768.
5.x also supports Filament 4, so you can move to Curator 5.x without changing Filament.
Full Changelog: https://github.com/awcodes/filament-curator/compare/v4.2.2...v4.2.3
This release contains security fixes for the 4.x line. Upgrading is recommended for every 4.x install. Details will be published in security advisorie…
This release contains security fixes for the 4.x line. Upgrading is recommended for every 4.x install. Details will be published in security advisories.
5.x also supports Filament 4, so you can move to Curator 5.x without changing Filament.
Check existing media for files stored under an unsafe extension, then repair them:
php artisan curator:repair-extensions --dry-run # report only
php artisan curator:repair-extensions
.txt.old -> new..JPG. Nothing is deleted.CannotUpdateLockedPropertyException.application/octet-stream, are accepted only when listed exactly, never through a wildcard such as text/*.view ability.base_url. Existing image URLs are unchanged._id.curator/ by default) is now served correctly..doc, .xls, .ppt) keep their type. .csv and .ics files detected as plain text get their own type.mb_ltrim, which isn't available on PHP 8.2 or 8.3 without a polyfill.CuratorPanel::setMediaForm() method.Added in #756, #757 and #758.
Full Changelog: https://github.com/awcodes/filament-curator/compare/v4.2.1...v4.2.2
Fixes an SVG sanitization bypass and unvalidated curation paths. See GHSA-3xm3-q2fj-x8rq for the full advisory.
Fixes an SVG sanitization bypass and unvalidated curation paths. See GHSA-3xm3-q2fj-x8rq for the full advisory.
payload.txt was stored unsanitized. Sanitizing now keys off the detected type as well as the extension, in both the uploader and CuratorUtils::importMedia, and the serving layer pins Content-Type from the stored extension instead of the sniffed bytes.saveCuration() consumed the crop payload unvalidated, so a key such as ../../other could overwrite a sibling file inside the storage disk. The payload is now validated before anything is written.curator:sanitize-svgs now selects on the detected type as well as the extension, so rows stored under a spoofed filename are no longer invisible to it.Re-scan stored media to clean up anything already on disk:
php artisan curator:sanitize-svgs --dry-run # report only
php artisan curator:sanitize-svgs
The serving-layer change already prevents affected rows from rendering as documents, so this is cleanup rather than the primary fix.
exif form view. It was not referenced anywhere in the package and could not render as shipped, since it requested an Alpine component that is never registered. If you published views with vendor:publish --tag=curator-views, your local copy is untouched by this removal and still contains a raw {!! !!} echo of EXIF metadata — escape or delete it.Reported by Afsana Alijabarova (@afa114).
The media picker's search now matches each term on its own instead of looking for the whole input as a single substring. A file named my-image.png cou
The media picker's search now matches each term on its own instead of looking for the whole input as a single substring. A file named my-image.png could not previously be found by typing "my image".
The search is split on whitespace, hyphens and underscores, and every term has to match — though any of the five searchable columns (name, title, alt, caption, description) may be the one matching it. So my-image.png is now found by "my image", "my_image", "my-image", or "image my", while my-document.png stays out of those results.
LIKE wildcards typed into the search are now escaped, so searching for 100% looks for a literal percent sign rather than matching everything. Worth knowing that _ has always been an unescaped single-character wildcard, so photo_8-sunset matched photo-8-sunset by accident while a hyphen did nothing; that inconsistency is gone.
Case sensitivity is still left to the database — Postgres LIKE is case-sensitive where MySQL and SQLite are not. That is unchanged from previous versions.
Thanks to @amywestlake for reporting this and proposing the original approach in #623.
Search results are now ordered by the panel's sort direction, matching the unfiltered list. There was no ORDER BY at all before, so the 50-row limit truncated an arbitrary slice of matches.
GliderFallback's setters were typed to require a value, while every property except the name is optional and every getter already returned null. Building a fallback from a conditional expression — the usual reason to have one — threw a TypeError in a service provider before the application could boot:
GliderFallback::make('logo')
->alt(config('app.name'))
->source(filled(setting('logo')) ? $logo->url : Vite::image('logo.webp'))
alt(), height(), source(), type() and width() now all accept null.
A registered fallback that ends up with no source still cannot be rendered, but it now names itself — The [logo] glider fallback does not have a source. — instead of reporting the media item as invalid, which pointed at the wrong thing.
Thanks again to @battulga0719 for reporting this in #718.
No changes are required for ordinary use. Two notes:
GliderFallback and overrode any of the setters with the narrower string/int signature, widen it to ?string/?int to match the parent.0 into the picker search previously reset the list to show everything. It now searches for "0"; whitespace-only input is what falls back to the unfiltered list.Applications that already set acceptedFileTypes() themselves — globally or per field — were never affected, because the vulnerable list was only used…
Curator's upload components fell back to a default list of accepted file types that included text/html, application/xhtml+xml, text/javascript, application/xml and application/octet-stream. An authenticated user with permission to upload media could upload an HTML file containing a <script> tag. The file was stored unmodified and later served from the application's own origin, executing the script with the session of whoever opened it.
This affected the Media resource form, MultiUploadAction, CuratorPicker and the rich editor's attachment flow, which all share the same default. Applications that already set acceptedFileTypes() themselves — globally or per field — were never affected, because the vulnerable list was only used as a fallback.
The default is now MimeType::defaults(): the full list minus types that are effectively executable content. MimeType::toArray() is unchanged, so code referencing the enum directly still works. As defense in depth, media served through Curator's own route now sends X-Content-Type-Options: nosniff, and restricted types are forced to Content-Disposition: attachment.
If your application genuinely needs to host these types, opt back in explicitly:
use Awcodes\Curator\Enums\MimeType;
Curator::acceptedFileTypes([...MimeType::defaults(), 'text/html']);
Note that Curator only sanitizes SVG uploads. Anything else you allow is stored and served verbatim, and with the default public disk it is also reachable through the storage symlink, where the new response headers do not apply. Serve deliberately-allowed executable types from a private disk.
The 3.x line is not affected — its accepted types come from config('curator.accepted_file_types'), whose default has always been limited to images and PDFs.
Glider fallbacks could not be used at all. Several faults compounded:
GliderFallback::make() passed the name through the container, but the class has no constructor, so Laravel discarded it. The name stayed null and getName() threw a TypeError, meaning a fallback built exactly as documented failed before it could be registered.<x-curator-glider> component rejected a null media item, which is the main reason to configure a fallback in the first place. It now accepts null.handleInt() checked the raw id rather than the looked-up record, so the fallback branch never ran and a missing record produced "Attempt to read property path on null" instead. The documented <x-curator-glider :media="1" fallback="thumbnail"/> could not work.Fallback resolution now happens in one place, so a null media item, an id that does not resolve, and a blank string all reach it. An unregistered fallback name, or one with no source, no longer dereferences null.
Also fixed while in there:
GliderFallback's optional getters were typed non-nullable while every property defaults to null, so a partially configured fallback threw. They are nullable now.GliderFallback::isPreviewable() called Curator::isResizable(), reporting svg sources as not previewable.Thanks to @battulga0719 for reporting the fallback issues in #717.
The media picker breadcrumb's root Disk label and the Selected Files heading in the selection modal were hardcoded in English and ignored the active l
curator::views.details.disk key, so it is already translated in every shipped locale.Adds a new attach_curator_media.modal.selected_files key under resources/lang/en/views.php. Other locales fall back to English until translated — contributions welcome.
Thanks to @Elgorm for reporting and fixing this in #716.
Fixes a broken access control vulnerability (CWE-862 / CWE-639, CVSS 7.6 High): the media picker modal's per-item Edit, Delete, and Download actions r…
Fixes a broken access control vulnerability (CWE-862 / CWE-639, CVSS 7.6 High): the media picker modal's per-item Edit, Delete, and Download actions resolved their target Media record from client-supplied input without a per-record authorization check or tenant scoping. Any authenticated user able to reach a form containing a CuratorPicker field could edit, delete, or download arbitrary Media records by id — bypassing any MediaPolicy the host app defines and Curator's own multi-tenancy scoping. The Download action also streamed a client-supplied disk/path directly.
These actions now enforce the resource's authorization policy per-record and apply the same tenant scoping used elsewhere in the picker, and Download streams from the stored record instead of the request payload. No configuration changes are required after upgrading.
See the security advisory for full details: https://github.com/awcodes/filament-curator/security/advisories/GHSA-3m5g-3j68-ghvp
Fixes a stored XSS vulnerability (CWE-79, CVSS 5.4 Moderate): SVG files uploaded through the Curator panel were served inline without sanitization, al…
Fixes a stored XSS vulnerability (CWE-79, CVSS 5.4 Moderate): SVG files uploaded through the Curator panel were served inline without sanitization, allowing embedded JavaScript to execute in the application's origin when a user opened the file via the View action. SVG uploads are now sanitized (scripts, event handlers, and remote references stripped) before being written to storage.
After upgrading, run php artisan curator:sanitize-svgs to clean any SVGs uploaded before
this release (use --dry-run to preview first).
See the security advisory for full details: https://github.com/awcodes/filament-curator/security/advisories/GHSA-8vm9-f75m-5h2m
enshrined/svg-sanitize.Fixes a cross-tenant media metadata disclosure in the Curator picker search. In multitenant panels, an authenticated user could retrieve other tenants
Fixes a cross-tenant media metadata disclosure in the Curator picker search. In multitenant panels, an authenticated user could retrieve other tenants' media metadata by typing in the picker search box. Single-tenant installs are not affected.
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:L/I:N/A:N)Upgrade recommended for any multitenant deployment. Also fixed in 3.7.8 and 5.1.1. A GitHub Security Advisory and CVE will be linked here once published.
Full Changelog: https://github.com/awcodes/filament-curator/compare/v4.1.0...v4.1.1
Fix cloud-disk (S3) support and curation modal handling by @awcodes in https://github.com/awcodes/filament-curator/pull/708
Full Changelog: https://github.com/awcodes/filament-curator/compare/v4.0.8...v4.1.0
Fix: navigation settings types by @awcodes in https://github.com/awcodes/filament-curator/pull/703
Full Changelog: https://github.com/awcodes/filament-curator/compare/v4.0.7...v4.0.8
Fix: accept UUIDs in curator panel by @awcodes in https://github.com/awcodes/filament-curator/pull/695
Full Changelog: https://github.com/awcodes/filament-curator/compare/v4.0.6...v4.0.7
Chore: improved test suite by @awcodes in https://github.com/awcodes/filament-curator/pull/684
Full Changelog: https://github.com/awcodes/filament-curator/compare/v4.0.5...v4.0.6
Fix: getVisibility() ignores config('curator.default_visibility') by @awcodes in https://github.com/awcodes/filament-curator/pull/682
Full Changelog: https://github.com/awcodes/filament-curator/compare/v4.0.4...v4.0.5
Fix: panel insert context scoping for rich editors by @awcodes in https://github.com/awcodes/filament-curator/pull/677
Full Changelog: https://github.com/awcodes/filament-curator/compare/v4.0.3...v4.0.4
Fix: glide server config in GlideManager and update upgrade guide by @awcodes in https://github.com/awcodes/filament-curator/pull/673
Full Changelog: https://github.com/awcodes/filament-curator/compare/v4.0.2...v4.0.3
Fix composer version constraints
Full Changelog: https://github.com/awcodes/filament-curator/compare/v4.0.1...v4.0.2
Fix: Use Curator facade to determine isResizable/isPreviewable by @adicacan in https://github.com/awcodes/filament-curator/pull/663
Full Changelog: https://github.com/awcodes/filament-curator/compare/v4.0.0...v4.0.1
Translated lang file into Italian by @Askancy in https://github.com/awcodes/filament-curator/pull/418
Full Changelog: https://github.com/awcodes/filament-curator/compare/v3.4.6...v4.0.0
Fix: reapply typeColumn and typeValue to picker by @awcodes in https://github.com/awcodes/filament-curator/pull/655
Full Changelog: https://github.com/awcodes/filament-curator/compare/v4.0.0-alpha.6...v4.0.0-alpha.7
Fix: styling issues by @awcodes in https://github.com/awcodes/filament-curator/pull/652
Full Changelog: https://github.com/awcodes/filament-curator/compare/v4.0.0-alpha.5...v4.0.0-alpha.6
Fix: insert after upload action in panel by @awcodes in https://github.com/awcodes/filament-curator/pull/650
Full Changelog: https://github.com/awcodes/filament-curator/compare/v4.0.0-alpha.4...v4.0.0-alpha.5
One column per quarter.