GHSA-8VM9-F75M-5H2M

Vulnerability from github – Published: 2026-11-17 20:54 – Updated: 2026-11-17 20:54
VLAI
Summary
Filament Curator: Stored XSS via unsanitized SVG upload served inline
Details

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

  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.

Show details on source website

{
  "affected": [
    {
      "database_specific": {
        "last_known_affected_version_range": "\u003c= 5.1.1"
      },
      "package": {
        "ecosystem": "Packagist",
        "name": "awcodes/filament-curator"
      },
      "ranges": [
        {
          "events": [
            {
              "introduced": "5.0.0"
            },
            {
              "fixed": "5.1.2"
            }
          ],
          "type": "ECOSYSTEM"
        }
      ]
    },
    {
      "database_specific": {
        "last_known_affected_version_range": "\u003c= 4.1.1"
      },
      "package": {
        "ecosystem": "Packagist",
        "name": "awcodes/filament-curator"
      },
      "ranges": [
        {
          "events": [
            {
              "introduced": "4.0.0"
            },
            {
              "fixed": "4.1.2"
            }
          ],
          "type": "ECOSYSTEM"
        }
      ]
    },
    {
      "database_specific": {
        "last_known_affected_version_range": "\u003c= 3.7.8"
      },
      "package": {
        "ecosystem": "Packagist",
        "name": "awcodes/filament-curator"
      },
      "ranges": [
        {
          "events": [
            {
              "introduced": "3.0.0"
            },
            {
              "fixed": "3.7.9"
            }
          ],
          "type": "ECOSYSTEM"
        }
      ]
    }
  ],
  "aliases": [
    "CVE-2026-69241"
  ],
  "database_specific": {
    "cwe_ids": [
      "CWE-284",
      "CWE-79"
    ],
    "github_reviewed": true,
    "github_reviewed_at": "2026-11-17T20:54:26Z",
    "nvd_published_at": null,
    "severity": "MODERATE"
  },
  "details": "## Summary\n\n  SVG files uploaded through the Curator media panel are stored and served inline without any\n  sanitization. An authenticated user with permission to upload media can upload an SVG\n  containing embedded JavaScript. When another panel user opens that file via the **View**\n  action (which opens the media as a top-level browser document), the embedded script executes\n  in the origin of the Filament application.\n\n  `image/svg+xml` is included in the default accepted MIME types, so a default installation is\n  affected unless SVG uploads have been explicitly disabled.\n\n  ## Impact\n\n  Because the SVG is served as a **top-level document** (not embedded in an `\u003cimg\u003e` tag), any\n  `\u003cscript\u003e`, event-handler attribute (e.g. `onload`), or `javascript:` URI inside it runs with\n  full script privileges in the application\u0027s origin. In a Filament admin context this can be\n  leveraged to:\n\n  - perform actions as the viewing user (typically a privileged administrator) via\n  authenticated same-origin requests,\n  - read same-origin data the victim\u0027s session can access,\n  - exfiltrate cookies/tokens not protected from script access.\n\n  The primary escalation path is a lower-privileged content author planting a payload that is\n  later triggered when a higher-privileged user clicks **View** on the file. Panel thumbnails\n  are **not** affected \u2014 they render through an `\u003cimg\u003e` tag, which does not execute SVG script.\n\n  ## Proof of concept\n\n  1. As a user who can upload media, upload an SVG file containing:\n\n     ```xml\n     \u003csvg xmlns=\"http://www.w3.org/2000/svg\" onload=\"alert(document.domain)\"\u003e\n       \u003crect width=\"100\" height=\"100\" fill=\"#fff\"/\u003e\n     \u003c/svg\u003e\n\n  2. In the Curator panel, click the View (eye) action for the uploaded file. The file opens as\n  a standalone document and the script executes in the application origin.\n\n  Patches\n\n  The fix sanitizes SVG markup at the upload choke point (Uploader), stripping scripts, event\n  handlers, and remote references before the file is written to storage. Sanitizing at the\n  source closes every serving path (the direct storage URL and the on-the-fly\n  Glide/MediaController fallback) without changing the default accepted MIME types.\n  Sanitization fails closed: if the markup cannot be parsed it is not stored.\n\n  A console command is included to re-sanitize SVG files already stored on disk from earlier\n  uploads:\n\n  php artisan curator:sanitize-svgs           # sanitize in place\n  php artisan curator:sanitize-svgs --dry-run # preview only\n\n  After upgrading to a patched release, run curator:sanitize-svgs to clean any SVGs uploaded\n  before the patch.\n\n  Workarounds\n\n  If you cannot upgrade immediately, either of the following mitigates the issue:\n\n  - Disallow SVG uploads \u2014 remove image/svg+xml from the accepted file types (e.g. via\n  acceptedFileTypes(...) on the Curator field/plugin), or\n  - Serve untrusted SVGs safely \u2014 configure your web server / storage responses to send stored\n  SVGs with Content-Disposition: attachment (or a Content-Security-Policy that blocks inline\n  script) so they cannot execute as a top-level document.\n\n  Credit\n\n  Reported via coordinated disclosure by [Afsana Alijabarova](https://github.com/afa114).",
  "id": "GHSA-8vm9-f75m-5h2m",
  "modified": "2026-11-17T20:54:26Z",
  "published": "2026-11-17T20:54:26Z",
  "references": [
    {
      "type": "WEB",
      "url": "https://github.com/awcodes/filament-curator/security/advisories/GHSA-8vm9-f75m-5h2m"
    },
    {
      "type": "WEB",
      "url": "https://github.com/awcodes/filament-curator/commit/7613e6ef4c4d716efdb5e3c8f65aca88256df1df"
    },
    {
      "type": "WEB",
      "url": "https://github.com/awcodes/filament-curator/commit/f0cf6520783aa82708cce30789835e7f48084291"
    },
    {
      "type": "PACKAGE",
      "url": "https://github.com/awcodes/filament-curator"
    },
    {
      "type": "WEB",
      "url": "https://github.com/awcodes/filament-curator/releases/tag/v3.7.9"
    },
    {
      "type": "WEB",
      "url": "https://github.com/awcodes/filament-curator/releases/tag/v4.1.2"
    },
    {
      "type": "WEB",
      "url": "https://github.com/awcodes/filament-curator/releases/tag/v5.1.2"
    }
  ],
  "schema_version": "1.4.0",
  "severity": [
    {
      "score": "CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:N",
      "type": "CVSS_V3"
    }
  ],
  "summary": "Filament Curator: Stored XSS via unsanitized SVG upload served inline"
}



Log in or create an account to share your comment.




Tags
Taxonomy of the tags.


Loading…

Loading…

Loading…

Forecast uses a logistic model when the trend is rising, or an exponential decay model when the trend is falling. Fitted via linearized least squares.

Sightings

Author Source Type Date Other

Nomenclature

  • Seen: The vulnerability was mentioned, discussed, or observed by the user.
  • Confirmed: The vulnerability has been validated from an analyst's perspective.
  • Published Proof of Concept: A public proof of concept is available for this vulnerability.
  • Exploited: The vulnerability was observed as exploited by the user who reported the sighting.
  • Patched: The vulnerability was observed as successfully patched by the user who reported the sighting.
  • Not exploited: The vulnerability was not observed as exploited by the user who reported the sighting.
  • Not confirmed: The user expressed doubt about the validity of the vulnerability.
  • Not patched: The vulnerability was not observed as successfully patched by the user who reported the sighting.

Loading…

Loading…

Loading…

Related by attack behaviour

Vulnerabilities whose description is nearest to this one in the vector space of the CIRCL/vulnerability-attack-technique-biencoder model. This is a similarity search over the bi-encoder space (plain cosine), not a classification, and it has no measured accuracy.


Loading…