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.
CVE-2026-69241
“—” beside the score: it is equal to the CVSS score beside it.
Score 5.4 from GitHub Security Advisory (severity: MODERATE) published 2026-11-17. A secondary CVSS source baseline 5.4; sources differ by 0.0.
Also known asEUVD-2026-127177 (ENISA EUVD) · GHSA-8vm9-f75m-5h2m (GitHub Security Advisories)Source: ENISA EUVD
- CISA's Vulnrichment rates exploitation as PoC; EchelonGraph holds no exploit-code reference for it
A fix is available — apply it.
- CVSS v3
- 5.4
- EG Score
- 5.4MEDIUMhigh confidence
- EG Risk
- 40EG Risk 40/100
EG Risk is EchelonGraph's 0–100 priority score. It fuses impact severity (EG Severity, the CVSS base score, never the KEV-floored or EPSS-lifted EG Score) with real-world exploitation and automatability, under weights EchelonGraph set by hand, so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner.
How it’s computed (value × EchelonGraph’s weight)Severity54% × 45%Impact severity (EG Severity): CVSS 5.4 of 10. Never the KEV-floored or EPSS-lifted EG Score.Exploitation40% × 40%EchelonGraph's fixed weight for EG-KEV Tier 3 (Elevated): a constant, not a probability.Automatability0% × 15%CISA's SSVC Automatable value: no (Vulnrichment).SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Track* at high (mission-essential systems).Exploitation public PoC (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.Action: A fix is available. Apply it within your standard update timelines. - EPSS PROB
- 0.3%
- EPSS %ILE
- 28th
- KEV
- Not listed
What the EG score is made of (scorer v4.0: the three questions the 0–10 score mixes, published apart · methodology)
The EG score (5.4): severity, escalated by confirmed exploitation. This CVE's 5.4 is its impact severity (EG Severity), not escalated.
- EG Severity
- 5.4 MEDIUMCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.GitHub Security Advisory CVSS
- EG Likelihood
- 0.3% within 30 daysSource: FIRST EPSS. FIRST's exploitation probability, not an EchelonGraph model.
- Confirmed exploitation
- None on record (CISA KEV, EG-KEV Tier 1)Reported apart from the likelihood: an observed fact, not a probability.
- EG Priority
- SSVC Track at medium mission impactTrack at low or medium mission impact; Track* at high (mission-essential systems).CISA BOD 26-04: 60 days if the affected system is publicly exposed; Fix on system upgrade if it is not.Each input and its source, and whom BOD 26-04 binds: the SSVC and BOD 26-04 blocks below.
SSVC (CISA's decision table, applied by EchelonGraph)Track at low or medium mission impact; Track* at high (mission-essential systems).
A fix is available. Apply it within your standard update timelines.
Exploitation public PoC (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table
BOD 26-04 (CISA's remediation timeline, Table 1)60 days if the affected system is publicly exposed; Fix on system upgrade if it is not.
The score's inputs: In CISA KEV no (CISA's KEV catalog) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it
Published
November 17, 2026
Last Modified
November 18, 2026
Advisory Details (6)
Auto-updated Nov 18, 2026Stored XSS via unsanitized SVG upload served inline · Advisory · awcodes/filament-curator · GitHub
https://github.com/awcodes/filament-curator/security/advisories/GHSA-8vm9-f75m-5h2mv5.1.2
Patch available: awcodes/filament-curator v5.1.2
https://github.com/awcodes/filament-curator/releases/tag/v5.1.2v4.1.2
Patch available: awcodes/filament-curator v4.1.2
https://github.com/awcodes/filament-curator/releases/tag/v4.1.2v3.7.9
Patch available: awcodes/filament-curator v3.7.9
https://github.com/awcodes/filament-curator/releases/tag/v3.7.9commit f0cf6520783a (awcodes/filament-curator)
Fix landed in awcodes/filament-curator commit f0cf6520783a — awaiting tagged release
https://github.com/awcodes/filament-curator/commit/f0cf6520783aa82708cce30789835e7f48084291commit 7613e6ef4c4d (awcodes/filament-curator)
Patch available: awcodes/filament-curator v5.3.1 (contains commit 7613e6ef4c4d)
https://github.com/awcodes/filament-curator/commit/7613e6ef4c4d716efdb5e3c8f65aca88256df1dfVendor Advisories for CVE-2026-69241(1)
These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.
Patch Availability(3)
| Vendor / Ecosystem | Fix (by version range) / Patch | Released | Source |
|---|---|---|---|
| composer | awcodes/filament-curator @ 5.1.2 (fixes >= 5.0.0, <= 5.1.1) | — | ghsa |
| composer | awcodes/filament-curator @ 4.1.2 (fixes >= 4.0.0, <= 4.1.1) | — | ghsa |
| composer | awcodes/filament-curator @ 3.7.9 (fixes >= 3.0.0, <= 3.7.8) | — | ghsa |
These rows come from GitHub (GHSA). Multiple rows for the same upstream release have been deduplicated.
Affected Packages
(1 across 1 ecosystem)
Packagist(1)
| Package | Vulnerable range | Fix by version range | Dependents |
|---|---|---|---|
| awcodes/filament-curator | v5.0.0 ... v5.1.1 (11 versions) |
| — |
Weakness Classification(2)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 10× in last 7d / 10× in last 30d)
Each row is a time one of our pipelines fetched, updated or re-scored this CVE. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed its CVE.org record (CNA or CISA ADP). An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). "EchelonGraph re-scored" is our own recompute of this CVE's score, not an update from a source, and is not counted in the refreshes above. Most recent first.
- 2026-11-21 16:40 UTCEPSS rescoreEPSS 0.3% · 28th percentile
- 2026-11-20 16:38 UTCEPSS rescoreEPSS 0.3% · 20th percentile
- 2026-11-19 16:35 UTCEPSS rescoreEPSS 0.3% · 20th percentile
- 2026-11-18 17:43 UTCEchelonGraph re-scored
- 2026-11-18 17:43 UTCGHSA enrichmentGHSA-8vm9-f75m-5h2m · GitHub severity MODERATE · GitHub CVSS 5.4
- 2026-11-18 17:29 UTCEchelonGraph re-scored
- 2026-11-18 17:29 UTCGHSA enrichmentGHSA-8vm9-f75m-5h2m · GitHub severity MODERATE · GitHub CVSS 5.4
- 2026-11-18 16:43 UTCEchelonGraph re-scored
- 2026-11-18 16:43 UTCGHSA enrichmentGHSA-8vm9-f75m-5h2m · GitHub severity MODERATE · GitHub CVSS 5.4
- 2026-11-18 16:35 UTCEPSS rescoreEPSS 0.3% · 24th percentile
- 2026-11-17 22:01 UTCEchelonGraph re-scored
- 2026-11-17 22:01 UTCGHSA enrichmentGHSA-8vm9-f75m-5h2m · GitHub severity MODERATE · GitHub CVSS 5.4
- 2026-11-17 20:03 UTCENISA EUVD ID recordedEUVD-2026-127177 · Source: ENISA EUVD
- 2026-11-17 19:28 UTCEchelonGraph re-scored
- 2026-11-17 18:54 UTCEchelonGraph re-scoredFirst assessed: 5.4 MEDIUM
- 2026-11-17 18:52 UTCMITRE cvelistV5first tracked
Related CVEs(same CWE)
Frequently asked(5)
What is CVE-2026-69241?
When was the CVE record for CVE-2026-69241 published?
Is CVE-2026-69241 actively exploited?
What is the CVSS score of CVE-2026-69241?
How do I remediate CVE-2026-69241?
Dependency Blast Radius
See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-69241
Is Your Infrastructure Affected by CVE-2026-69241?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.