cve.bz

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

5.4 mediumFix available

Medium (5.4) in awcodes filament-curator. Fixed in awcodes/filament-curator 3.7.9, 4.1.2, 5.1.2.

On this page
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.

Severity

CVSS 3.1

5.4 medium
CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:N
CWEs
CWE-79 Improper Neutralization of Input During Web Page Generation (Cross-site Scripting)
CWE-284 Improper Access Control
OWASP Top 10
A01:2025 Broken Access Control, A05:2025 Injection
Published
Assigned by
GitHub_M (CNA)
NVD analysis
Awaiting analysis
Record from
the NVD, synced

Fix and patched versions

  • awcodes/filament-curator (Packagist): fixed in 5.1.2, 4.1.2, 3.7.9

Ask an AI about this CVE

Show the promptExplain CVE-2026-69241 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-69241?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-69241?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2026-69241 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Affected

Versions

From the CNA's record in the CVE List.

ProductAffected
awcodes filament-curator>= 3.0.0, < 3.7.9
awcodes filament-curator>= 4.0.0, < 4.1.2
awcodes filament-curator>= 5.0.0, < 5.1.2

Packages (OSV)

AdvisoryEcosystemPackageAffectedFixed in
GHSA-8vm9-f75m-5h2mPackagistawcodes/filament-curator>=5.0.0 <5.1.25.1.2
GHSA-8vm9-f75m-5h2mPackagistawcodes/filament-curator>=4.0.0 <4.1.24.1.2
GHSA-8vm9-f75m-5h2mPackagistawcodes/filament-curator>=3.0.0 <3.7.93.7.9

Attack patterns (CAPEC)

  • CAPEC-63 Cross-Site Scripting (XSS) Likelihood: High · Severity: Very High
  • CAPEC-85 AJAX Footprinting Likelihood: High · Severity: Low
  • CAPEC-209 XSS Using MIME Type Mismatch Severity: Medium
  • CAPEC-588 DOM-Based XSS Likelihood: High · Severity: Very High
  • CAPEC-591 Reflected XSS Likelihood: High · Severity: Very High
  • CAPEC-592 Stored XSS Likelihood: High · Severity: Very High

The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits. More on the page of CWE-284 (17).

References

Check your stackJSON