CVE-2026-69241: Filament Curator: Stored XSS via unsanitized SVG upload served inline

Published Nov 17, 2026
·
Updated

Summary

SVG files uploaded through the Curator media panel are stored and served inline without any sanitization. An authenticated user with permission to upload media can upload an SVG containing embedded JavaScript. When another panel user opens that file via the View action (which opens the media as a top-level browser document), the embedded script executes in the origin of the Filament application.

image/svg+xml is included in the default accepted MIME types, so a default installation is affected unless SVG uploads have been explicitly disabled.

## Impact

Because the SVG is served as a top-level document (not embedded in an <img> tag), any <script>, event-handler attribute (e.g. onload), or javascript: URI inside it runs with full script privileges in the application's origin. In a Filament admin context this can be leveraged to:

- perform actions as the viewing user (typically a privileged administrator) via authenticated same-origin requests, - read same-origin data the victim's session can access, - exfiltrate cookies/tokens not protected from script access.

The primary escalation path is a lower-privileged content author planting a payload that is later triggered when a higher-privileged user clicks View on the file. Panel thumbnails are not affected — they render through an <img> tag, which does not execute SVG script.

## Proof of concept

1. As a user who can upload media, upload an SVG file containing:

xml <svg xmlns="http://www.w3.org/2000/svg" onload="alert(document.domain)"> <rect width="100" height="100" fill="#fff"/> </svg>

2. In the Curator panel, click the View (eye) action for the uploaded file. The file opens as a standalone document and the script executes in the application origin.

Patches

The fix sanitizes SVG markup at the upload choke point (Uploader), stripping scripts, event handlers, and remote references before the file is written to storage. Sanitizing at the source closes every serving path (the direct storage URL and the on-the-fly Glide/MediaController fallback) without changing the default accepted MIME types. Sanitization fails closed: if the markup cannot be parsed it is not stored.

A console command is included to re-sanitize SVG files already stored on disk from earlier uploads:

php artisan curator:sanitize-svgs # sanitize in place php artisan curator:sanitize-svgs --dry-run # preview only

After upgrading to a patched release, run curator:sanitize-svgs to clean any SVGs uploaded before the patch.

Workarounds

If you cannot upgrade immediately, either of the following mitigates the issue:

- Disallow SVG uploads — remove image/svg+xml from the accepted file types (e.g. via acceptedFileTypes(...) on the Curator field/plugin), or - Serve untrusted SVGs safely — configure your web server / storage responses to send stored SVGs with Content-Disposition: attachment (or a Content-Security-Policy that blocks inline script) so they cannot execute as a top-level document.

Credit

Reported via coordinated disclosure by Afsana Alijabarova.

Other sources

Filament Curator is a media picker plugin for Filament panels. From 3.0.0 until 3.7.9, 4.1.2, and 5.1.2, the Curator media panel accepts image/svg+xml files by default and stores and serves their markup inline without sanitization. An authenticated user with media-upload permission can store an SVG containing scripts, event-handler attributes, or javascript: URIs. When another panel user selects the View action, the SVG opens as a top-level browser document and its active content executes in the Filament application's origin. The script can perform authenticated same-origin actions as the viewing user and read same-origin data and script-accessible tokens. Panel thumbnails are not affected because they render through an image element that does not execute SVG script. This issue is fixed in versions 3.7.9, 4.1.2, and 5.1.2.

— MITRE

Affected Software

7 affected componentsFixes available
composer/awcodes/filament-curator>=3.0.0<3.7.9, >=4.0.0<4.1.2, >=5.0.0<5.1.2
composer/awcodes/filament-curator>=3.0.0<=3.7.8
3.7.9
composer/awcodes/filament-curator>=4.0.0<=4.1.1
4.1.2
composer/awcodes/filament-curator>=5.0.0<=5.1.1
5.1.2
composer/awcodes/filament-curator>=5.0.0<5.1.2
5.1.2
composer/awcodes/filament-curator>=4.0.0<4.1.2
4.1.2
composer/awcodes/filament-curator>=3.0.0<3.7.9
3.7.9

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade composer/awcodes/filament-curator to a version that resolves this vulnerability.

    Fixed in 3.7.9
  2. Upgrade

    Upgrade composer/awcodes/filament-curator to a version that resolves this vulnerability.

    Fixed in 4.1.2
  3. Upgrade

    Upgrade composer/awcodes/filament-curator to a version that resolves this vulnerability.

    Fixed in 5.1.2
  4. Upgrade

    Upgrade to a fixed release to a version that resolves this vulnerability.

    Fixed in 3.7.9
  5. Upgrade

    Upgrade to a fixed release to a version that resolves this vulnerability.

    Fixed in 4.1.2
  6. Upgrade

    Upgrade to a fixed release to a version that resolves this vulnerability.

    Fixed in 5.1.2
  7. Configuration

    Remove image/svg+xml from the accepted file types for the Curator field or plugin.

    Filament Curator acceptedFileTypes = exclude image/svg+xml
  8. Configuration

    Serve stored SVG files with Content-Disposition: attachment so they cannot execute as top-level documents.

    Web server or storage responses for SVG files Content-Disposition = attachment
  9. Operational

    After upgrading, run php artisan curator:sanitize-svgs to sanitize SVG files already stored on disk.

Event History

Nov 17, 2026
CVE Published
via MITRE·06:46 PM
Data Sourced
via MITRE·06:46 PM
DescriptionSeverityWeakness
Data Sourced
via NVD·07:18 PM
DescriptionSeverityWeakness
Advisory Published
via GitHub·08:54 PM
Data Sourced
via GitHub·08:54 PM
DescriptionSeverityWeaknessAffected Software
Data Sourced
via OSV·08:54 PM
Affected Software

Frequently Asked Questions

1

Who can exploit this issue and who is at risk from the stored payload?

An authenticated user with media-upload permission can upload a malicious SVG. A different panel user is affected when they use the View action on that SVG; the script then executes with that viewer's same-origin access.

2

Are default installations affected?

Yes. The Curator media panel accepts image/svg+xml files by default, and affected versions store and serve SVG markup inline without sanitization.

3

Do thumbnails trigger the malicious SVG?

No. Thumbnails render SVGs through an image element, which does not execute SVG script. The active content executes when a panel user opens the file with the View action.

4

What could the malicious script do in a viewer's session?

It can perform authenticated same-origin actions as the viewing user and read same-origin data and script-accessible tokens.

5

Which versions contain the fix?

The issue is fixed in versions 3.7.9, 4.1.2, and 5.1.2.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203