CVE-2026-48557: Spatie Laravel Media Library < 11.23.0 File Upload Restriction Bypass via FileAdder.php
Spatie Laravel Media Library before version 11.23.0 contains a file upload restriction bypass in FileAdder::defaultSanitizer(). The sanitizer checks only the final filename suffix, allowing double-extension filenames such as shell.php.jpg to bypass the blocklist, with pathinfo() preserving inner .php stems in saved filenames. The blocklist also omits executable extensions including .php6, .shtml, and .htaccess. The double-extension bypass requires a legacy Apache AddHandler configuration to achieve PHP execution; the incomplete blocklist bypass does not.
Security readout for executives and security teams
Plain-English summary
Applications using Spatie Laravel Media Library before 11.23.0 may accept filenames intended to be blocked. If attackers can upload media, unsafe files could be stored and, under certain server configurations, executed. Successful exploitation could compromise application data, integrity, and availability.
Executive priority
Prioritize remediation for internet-facing applications with user uploads, especially where low-privileged accounts can submit files. Upgrade promptly and verify that upload storage cannot execute content. Applications without attacker-accessible uploads have lower immediate exposure, but should still update because the vulnerable sanitizer remains present.
Technical view
FileAdder::defaultSanitizer() checks only the final suffix, so double extensions can evade its blocklist while pathinfo() preserves an executable inner extension. The blocklist also omits .php6, .shtml, and .htaccess. Double-extension PHP execution requires legacy Apache AddHandler configuration; the omitted-extension bypass does not require that configuration.
Likely exposure
Exposure is most likely where versions before 11.23.0 process attacker-controlled uploads. Risk increases when upload capability is available to low-privileged accounts and stored files are served through execution-capable web-server paths. Actual impact depends on application upload controls and hosting configuration.
Exploitation context
The CVSS 3.1 score is 8.8, reflecting network access, low complexity, low privileges, no user interaction, and potentially severe impact. The supplied record is not in KEV, and the provided sources do not establish active exploitation. One execution path specifically depends on legacy Apache AddHandler behavior.
Researcher notes
This is CWE-184: an incomplete list of disallowed inputs. Assessment should distinguish the double-extension path from omitted blocklist extensions because their configuration dependencies differ. The supplied evidence supports the vulnerable behavior and patched release, but does not demonstrate exploitation in the wild or establish exposure for any specific deployment.
Mitigation direction
Upgrade Spatie Laravel Media Library to version 11.23.0 or later.
Restrict upload access to trusted users until the upgrade is verified.
Prevent uploaded media directories from executing server-side content.
Apply independent allowlists for permitted extensions, MIME types, and expected file content.
Review vendor release notes and patch details for application-specific deployment guidance.
Validation and detection
Identify the installed laravel-medialibrary version from application dependency records.
Map every endpoint that passes attacker-controlled files into the media library.
Verify authorization requirements for each upload path, including low-privileged roles.
Review Apache configuration for legacy AddHandler behavior affecting uploaded files.
Inspect historical uploads for double extensions and omitted executable extensions.
Confirm version 11.23.0 or later is deployed across every application instance.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
cwe · low confidence lookup
CWE-184: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
The CVE wording references file access or upload behavior, so file telemetry and web shell review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
2CVSS vectors
3Timeline events
1ADP providers
5Source links
SSVC decision data
CISA-ADPCISA Coordinator
Timestamp
Version
2.0.3
Exploitation: noneAutomatable: noTechnical Impact: total
CVSS vector scores
2 official scores
We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
CWE-184 · source CWE mapping
Incomplete List of Disallowed Inputs
Incomplete List of Disallowed Inputs represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.