CVEReports
CVEReports

Automated vulnerability intelligence platform. Comprehensive reports for high-severity CVEs generated by AI.

Product

  • Home
  • Sitemap
  • RSS Feed

Company

  • About
  • Contact
  • Privacy Policy
  • Terms of Service

© 2026 CVEReports. All rights reserved.

Made with love by Amit Schendel & Alon Barad



CVE-2026-69241

CVE-2026-69241: Stored Cross-Site Scripting via Unsanitized SVG Upload in Filament Curator

Alon Barad
Alon Barad
Software Engineer

Nov 17, 2026·9 min read·2 visits

Executive Summary (TL;DR)

Authenticated users with media upload permissions can upload SVG files containing embedded JavaScript to Filament Curator. When another user clicks the 'View' action on the uploaded media, the script executes in the application's origin, enabling session hijacking and unauthorized state-changing operations. Upgrade to versions 3.7.9, 4.1.2, or 5.1.2 and run php artisan curator:sanitize-svgs to remediate.

Filament Curator, a media picker plugin for Filament panels in Laravel applications, contains a Stored Cross-Site Scripting (XSS) vulnerability in versions prior to 3.7.9, 4.1.2, and 5.1.2. The application accepts image/svg+xml uploads by default and stores them on disk without stripping executable XML markup. When a panel user opens an uploaded SVG via the View action, the file renders as a top-level document in the browser, executing embedded JavaScript within the origin of the Filament application.

Vulnerability Overview

Filament Curator (awcodes/filament-curator) is a media management and picker plugin designed for Filament administration panels in Laravel applications. It provides an interface for uploading, organizing, and embedding media assets across administrative workflows. By default, the plugin's configuration permits the upload of various image formats, including Scalable Vector Graphics (image/svg+xml).

In versions prior to 3.7.9, 4.1.2, and 5.1.2, the file upload handler writes user-supplied SVG files directly to disk without parsing or sanitizing their XML structure. Because the SVG specification is based on XML, valid SVG documents can include executable elements such as <script> blocks, inline event handler attributes (e.g., onload, onerror), and javascript: URI schemes inside anchor elements.

This weakness is classified under CWE-79 (Improper Neutralization of Input During Web Page Generation). While media thumbnails inside the Curator administration grid are rendered inside standard HTML <img> elements—which browsers restrict from executing scripts—selecting the "View" action navigates the browser directly to the raw SVG file URL.

When the browser loads the SVG as a top-level document with the Content-Type: image/svg+xml header, it constructs an interactive XML DOM and executes any embedded scripts. Because the media asset is typically served from the local storage disk on the same domain as the Filament panel, the script executes within the application's security origin. This allows a lower-privileged user with upload permissions to execute arbitrary JavaScript in the session context of a higher-privileged administrator.

Root Cause Analysis

The root cause of CVE-2026-69241 is the absence of server-side XML sanitization during the file upload lifecycle in Awcodes\Curator\Components\Forms\Uploader. When a user submits a file through the Curator upload component, the file stream is passed to Laravel's filesystem storage adapter and written directly to the configured disk.

For raster image formats like JPEG, PNG, and WebP, Curator routes image manipulation requests through league/glide, which re-encodes image data when generating thumbnails or transformations. However, vector graphics cannot be processed by Glide and are bypassed entirely during image transformation pipelines. Consequently, the exact byte sequence provided by the client during upload is preserved on disk and served verbatim when requested.

Triggering the vulnerability requires two distinct stages: storage and top-level rendering. During the storage phase, the uploader validates the file extension and MIME type against the allowed configuration list, which includes image/svg+xml by default. No content inspection occurs at this boundary.

During the rendering phase, the Curator media resource panel provides a "View" button for each stored asset. Clicking this button directs the user's browser to the asset's public storage URL or the MediaController fallback route. Because the response does not enforce a Content-Disposition: attachment header or a restrictive Content Security Policy (CSP), the browser interprets the document as active markup and executes the attacker's payload.

Code Analysis

The remediation introduced in commit 7613e6ef4c4d716efdb5e3c8f65aca88256df1df addresses the vulnerability by integrating the enshrined/svg-sanitize library into the upload choke point and providing a CLI utility for existing files. First, the package adds a dedicated sanitization method to the configuration trait Awcodes\Curator\Config\Concerns\HasSanitizers (and src/helpers.php in the 3.x branch).

use enshrined\svgSanitize\Sanitizer;
 
/**
 * Strip scripts, event handlers and remote references from SVG markup so it
 * cannot execute JavaScript when served inline as a top-level document.
 */
public function sanitizeSvg(string $svg): string
{
    $sanitizer = new Sanitizer;
    // Prevent external resource fetching (SSRF/tracking) via SVG links
    $sanitizer->removeRemoteReferences(true);
 
    $clean = $sanitizer->sanitize($svg);
 
    // Fail closed: if XML parsing fails, return an empty string rather than raw input
    return $clean === false ? '' : $clean;
}

Next, src/Components/Forms/Uploader.php is modified within the setUp() method where uploaded files are persisted to disk. Immediately after the initial file write completes, the component checks if the file extension corresponds to an SVG and overwrites the file on disk with its sanitized output.

// Vulnerable code path (pre-patch): File is saved and metadata is immediately returned
$path = $file->storeAs(
    $component->getDirectory(),
    $filename,
    $component->getDiskName()
);
 
// Patched code path: Intercept SVG files immediately after storage
if (Curator::isSvg($extension)) {
    $disk = Storage::disk($component->getDiskName());
    // Read stored content, strip executable XML nodes/attributes, and overwrite
    $disk->put($path, Curator::sanitizeSvg($disk->get($path)), $component->getVisibility());
    // Recalculate file size after stripping malicious markup
    $size = $disk->size($path);
}

The patch also introduces Awcodes\Curator\Commands\SanitizeSvgsCommand (curator:sanitize-svgs) to clean files uploaded prior to the upgrade. While sanitizeSvg() fails closed by returning an empty string on malformed XML during new uploads, the retroactive command explicitly checks for empty return values (if ($clean === '' && $original !== '')) and skips unparseable files to avoid accidental data destruction on existing disks.

> [!NOTE] > Fix Completeness Assessment: Performing sanitization at the storage choke point (Uploader::saveUploadedFileUsing) ensures that both direct public disk URLs and fallback controller routes serve clean files. However, notice that in Uploader.php, the file is briefly written to disk before being read back and overwritten with the sanitized version. On local filesystems, this window is negligible, though in high-latency remote object storage (e.g., S3), a tiny race window exists between initial write and overwrite.

Exploitation

Exploiting CVE-2026-69241 requires an authenticated account with privileges to access a Filament panel and upload media via the Curator plugin. In multi-user applications, roles such as Content Authors, Contributors, or Support Agents frequently possess media upload rights while lacking administrative control over users or system settings.

To execute the attack, the adversary crafts a valid SVG file containing an embedded JavaScript payload. The payload can utilize standard <script> tags or event handlers attached to graphical elements.

<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<svg xmlns="http://www.w3.org/2000/svg" width="200" height="200" onload="executePayload()">
  <script type="text/javascript"><![CDATA[
    function executePayload() {
      // Fetch the Filament panel DOM or read CSRF tokens from cookies/storage
      fetch('/admin/users/create', {
        method: 'GET',
        credentials: 'include'
      })
      .then(response => response.text())
      .then(html => {
        console.log('Successfully read administrative route content in origin:', document.domain);
      });
    }
  ]]></script>
  <rect width="200" height="200" fill="#3b82f6" />
</svg>

The attacker uploads this file through the Curator media picker or the dedicated Media resource page. The server accepts the image/svg+xml MIME type and stores the file under the configured public directory (e.g., /storage/media/payload.svg).

When a victim user, such as a site administrator, browses the media library, the SVG thumbnail renders harmlessly inside an <img> tag. However, if the administrator inspects the asset by clicking the View action, or navigates directly to /storage/media/payload.svg, the browser opens the file as a standalone document. The executePayload() function immediately triggers with full access to the administrator's cookies (excluding HttpOnly cookies), localStorage, and same-origin HTTP endpoints, allowing the script to forge Livewire requests or extract sensitive application data.

Impact Assessment

The vulnerability carries a CVSS v3.1 base score of 5.4 (Medium) with the vector CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:N. The Attack Complexity is Low (AC:L) because no special configuration is required; Filament Curator enables image/svg+xml uploads in its default configuration out of the box. Privileges Required is Low (PR:L), reflecting the requirement for an authenticated panel session with media upload capabilities.

User Interaction is Required (UI:R) because an administrative user or peer must actively open the malicious SVG as a top-level document via the "View" action. The Scope is Changed (S:C) because the vulnerability resides in the server-side media component but executes within the client's web browser security context.

In a standard Laravel and Filament deployment, session cookies are configured with the HttpOnly flag enabled by default, which prevents the injected JavaScript from directly reading the raw session identifier via document.cookie. However, the XSRF-TOKEN cookie used by Laravel for Cross-Site Request Forgery protection is intentionally accessible to JavaScript.

Consequently, an attacker's script running in the same origin can read the XSRF-TOKEN or scrape Livewire CSRF tokens directly from same-origin panel pages using fetch() with credentials: 'include'. This allows the attacker to perform arbitrary authenticated actions on behalf of the viewing administrator, including privilege escalation, user account creation, or data exfiltration from administrative views.

Remediation

To remediate CVE-2026-69241, upgrade awcodes/filament-curator to the patched release corresponding to your installed major version: 3.7.9 (for 3.x), 4.1.2 (for 4.x), or 5.1.2 (for 5.x). Update the package using Composer:

composer update awcodes/filament-curator

Because upgrading the package only sanitizes newly uploaded files, administrators must also sanitize existing SVG files already stored on disk. The patched versions include an Artisan command specifically for this purpose. First, run the command with the --dry-run flag to audit existing assets, then execute the sanitization pass:

# Audit existing SVG files without modifying disk contents
php artisan curator:sanitize-svgs --dry-run
 
# Sanitize all stored SVG files and update database file size records
php artisan curator:sanitize-svgs

> [!NOTE] > If curator:sanitize-svgs encounters an SVG file with corrupted or unparseable XML, it logs a warning (skipped (could not sanitize)) and leaves the file untouched. Administrators should manually inspect and remove any skipped files reported by the command.

For environments where immediate upgrading is not possible, or as a defense-in-depth measure, administrators can take two additional steps:

  1. Restrict Accepted File Types: Remove image/svg+xml from the accepted_file_types array in the config/curator.php configuration file if vector graphics are not required.
  2. Web Server Headers: Configure the web server (Nginx or Apache) or object storage bucket serving /storage/ routes to send Content-Disposition: attachment and Content-Security-Policy: default-src 'none'; style-src 'unsafe-inline' headers whenever serving .svg files. This forces the browser to download the file or blocks script execution when viewed inline.

Official Patches

awcodesFilament Curator v3.7.9 Release
awcodesFilament Curator v4.1.2 Release
awcodesFilament Curator v5.1.2 Release

Fix Analysis (2)

Technical Appendix

CVSS Score
5.4/ 10
CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:N

Affected Systems

awcodes/filament-curator

Affected Versions Detail

Product
Affected Versions
Fixed Version
filament-curator
awcodes
>= 3.0.0, < 3.7.93.7.9
filament-curator
awcodes
>= 4.0.0, < 4.1.24.1.2
filament-curator
awcodes
>= 5.0.0, < 5.1.25.1.2
AttributeDetail
Vulnerability TypeStored Cross-Site Scripting (Stored XSS)
CWE IDCWE-79 / CWE-284
CVSS v3.1 Score5.4 (Medium)
Attack VectorNetwork (Authenticated Media Upload)
Affected ComponentAwcodes\Curator\Components\Forms\Uploader
Patched Versions3.7.9, 4.1.2, 5.1.2
Exploit StatusNo known public exploits
KEV StatusNot Listed

MITRE ATT&CK Mapping

T1189Drive-by Compromise
Initial Access
T1185Browser Session Hijacking
Collection
CWE-79
Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting')

The software does not neutralize or incorrectly neutralizes user-controllable input before it is placed in output that is used as a web page that is served to other users.

Vulnerability Timeline

CVE-2026-69241 and GHSA-8vm9-f75m-5h2m published; patches released in v3.7.9, v4.1.2, and v5.1.2
2026-04-14

References & Sources

  • [1]GitHub Security Advisory GHSA-8vm9-f75m-5h2m
  • [2]Patch Commit (4.x / 5.x): Sanitize SVG uploads to prevent stored XSS
  • [3]Patch Commit (3.x): Sanitize SVG uploads to prevent stored XSS
  • [4]Filament Curator v3.7.9 Release Notes
  • [5]Filament Curator v4.1.2 Release Notes
  • [6]Filament Curator v5.1.2 Release Notes
  • [7]NVD - CVE-2026-69241
  • [8]CVE.org Record - CVE-2026-69241
  • [9]CVE List V5 JSON Record

Attack Flow Diagram

Press enter or space to select a node. You can then use the arrow keys to move the node around. Press delete to remove it and escape to cancel.
Press enter or space to select an edge. You can then press delete to remove it or escape to cancel.

More Reports

•about 4 hours ago•CVE-2026-63182
8.1

CVE-2026-63182: XML Signature Wrapping Authentication Bypass in LightSAML

CVE-2026-63182 is a high-severity XML Signature Wrapping (XSW) vulnerability in LightSAML (litesaml/lightsaml), a PHP library implementing SAML 2.0 data models and cryptographic verification. An architectural discrepancy between how LightSAML deserializes direct child assertions and how the underlying robrichards/xmlseclibs library resolves XML document fragment identifiers allows an attacker with a valid signed assertion to forge arbitrary SAML identity claims and bypass authentication.

Alon Barad
Alon Barad
4 views•11 min read
•about 5 hours ago•CVE-2026-119351
6.3

CVE-2026-119351: Cross-Context Cache Leak via Delayed Inner Stream Metadata in Next.js

A race condition and improper synchronization vulnerability (CWE-362) exists in Next.js versions 16.2.0 prior to 16.4.5 when Cache Components ('use cache' directive) are enabled. When an outer cached function calls a nested cached function that reads dynamic root parameters via 'next/root-params' and returns an object containing pending promises, React Flight can resolve and deliver the ready portion of the payload before the inner cache finishes publishing its root parameter dependencies. Consequently, the outer cache entry finalizes and persists under a cache key that omits the root parameter dependencies, causing the first written cache entry to be served across requests with different root parameter values and bypassing nested cache invalidation rules.

Amit Schendel
Amit Schendel
7 views•10 min read
•about 6 hours ago•CVE-2026-68934
8.7

CVE-2026-68934: OS Command Injection in code-review-mcp-server via Unsafe Shell Execution

A remote OS command injection vulnerability (CWE-78) exists in code-review-mcp-server prior to version 1.5.3. The application passes caller-controlled tool parameters directly into Node.js child_process.execSync() calls without proper neutralization. An attacker or compromised LLM agent invoking tools such as getLocalGitDiff, codeReview, createPR, or getPRTemplate can inject arbitrary shell commands that execute with the privileges of the MCP server host process.

Alon Barad
Alon Barad
7 views•11 min read
•about 7 hours ago•CVE-2026-86046
7.1

CVE-2026-86046: Arbitrary File Write via Path Traversal in termux-sync Restore Workflow

A path traversal vulnerability (CWE-22) in termux-sync prior to version 1.2.4 allows an attacker to overwrite arbitrary files within the Termux environment during the backup restoration process. The flaw stems from the application trusting attacker-controlled extraction paths defined in the backup's manifest.json file, failing to validate archive members against directory traversal sequences during tar extraction, and using unsanitized backup names when constructing temporary directories. If a user restores a malicious backup archive from local storage, shared folders, GitHub, or Google Drive, an attacker can overwrite sensitive configuration files such as shell startup scripts or local binaries, resulting in arbitrary code execution under the privileges of the Termux user.

Amit Schendel
Amit Schendel
6 views•11 min read
•about 8 hours ago•CVE-2026-129296
6.5

CVE-2026-129296: Path Traversal in SpamScope mail-parser Attachment Extraction

SpamScope mail-parser versions 3.8.0 prior to 4.6.0 contain a path traversal vulnerability (CWE-22) within the write_attachments() and write_sample() functions. The library passes untrusted attachment filenames directly into os.path.join() without stripping directory components, validating path containment, or verifying symbolic links. An attacker can send a crafted email containing relative path traversal sequences or absolute filesystem paths in the Content-Disposition header to write or overwrite arbitrary files accessible to the parsing process.

Amit Schendel
Amit Schendel
4 views•9 min read
•about 9 hours ago•CVE-2026-129295
7.5

CVE-2026-129295: Polynomial Regular Expression Denial of Service (ReDoS) in SpamScope mail-parser

A Regular Expression Denial of Service (ReDoS) vulnerability exists in SpamScope mail-parser versions 4.2.0 prior to 4.6.1. Two separate regular expressions evaluated during standard email header parsing exhibit quadratic to cubic backtracking complexity when processing headers padded with whitespace or angle brackets. An unauthenticated remote attacker can exploit this flaw by sending a small, RFC-compliant email message, causing parsing worker threads or processes to stall at 100% CPU utilization for extended periods.

Amit Schendel
Amit Schendel
4 views•10 min read