# Spatie Laravel Media Library contains a file upload restriction bypass

Advisory record · `GHSA-3ggm-c5m7-hfv5`

- **Identifiers:** `GHSA-3ggm-c5m7-hfv5` · `CVE-2026-48557` · `PKSA-mrgr-9pdf-y591`
- **State:** Confirmed
- **Severity:** CVSS 8.7 High
- **Critical:** No
- **Weakness (CWE):** [CWE-184](https://cwe.mitre.org/data/definitions/184.html)
- **Tags:** [CWE-184](https://agentprime.io/advisories/tag/cwe-184.md)
- **Published:** 29 May 2026
- **Updated:** 10 Sept 2026
- **Reviewed by a person:** No

Published by the GitHub Advisory Database at 29 May 2026, 21:31 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

## Affected packages

- `spatie/laravel-medialibrary` (Packagist): affected `<11.23.0`; fixed in `11.23.0`

## Machine-written summary

Summary written by Claude Haiku from the source advisory. Not reviewed by a person.

> Spatie Laravel Media Library versions before 11.23.0 have a file upload restriction bypass in FileAdder::defaultSanitizer(), whose blocklist checks only the final filename suffix and omits some executable extensions such as .php6, .shtml, and .htaccess. An attacker who can upload files could use a double-extension name like shell.php.jpg to get past the filter, and the source says this leads to PHP execution only where a legacy Apache AddHandler configuration is present. Upgrade to spatie/laravel-medialibrary 11.23.0 or later.

Written 31 Oct 2026.

## Not analysed yet

We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check.

## Severity and exploitation

- 8.7 High, CVSS 4.0: `CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N`, from CNA (VulnCheck)

- **CISA KEV:** Not listed.
- **EPSS:** 0.0044, the 38th percentile, on 9 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

## Timeline

- 29 May 2026, 19:49 UTC: [Confirmed by the CVE List](https://www.cve.org/CVERecord?id=CVE-2026-48557)
- 31 Oct 2026, 14:02 UTC: First seen by agentprime
- 31 Oct 2026, 14:02 UTC: [Confirmed by OSV](https://osv.dev/vulnerability/GHSA-3ggm-c5m7-hfv5)

## Sources

- [GitHub Advisory Database: GHSA-3ggm-c5m7-hfv5](https://github.com/advisories/GHSA-3ggm-c5m7-hfv5)
- [OSV: GHSA-3ggm-c5m7-hfv5](https://osv.dev/vulnerability/GHSA-3ggm-c5m7-hfv5)
- <https://nvd.nist.gov/vuln/detail/CVE-2026-48557>
- <https://github.com/spatie/laravel-medialibrary/pull/3939>
- <https://github.com/spatie/laravel-medialibrary/commit/608ea03703d3887c46434f5dda6af56de6346aba>
- <https://github.com/spatie/laravel-medialibrary>
- <https://github.com/spatie/laravel-medialibrary/releases/tag/11.23.0>
- <https://www.vulncheck.com/advisories/spatie-laravel-media-library-file-upload-restriction-bypass-via-fileadder-php>

Facts on this page come from the GitHub Advisory Database (CC-BY 4.0), OSV and the other sources listed, as published. We don’t reproduce full advisory descriptions, which can contain exploit code.

## Check whether this affects you

A Match means an installed version is in the affected range above. Most don’t affect the app; agentprime hasn’t analysed this one yet.

- With the agentprime MCP server (<https://api.agentprime.io/mcp>), ask your agent to check the project: `check_lockfile` sends a lockfile, `check_packages` a list of installed packages, and both return the Matches and the upgrades that clear them. `get_advisory` returns this record. Setup: <https://agentprime.io/mcp.md>
- In a browser: <https://agentprime.io/check/> reads your lockfile in the browser, never uploading it.
- Whether it touches your code, with file and line: the Claude Code plugin, <https://agentprime.io/plugin.md>
- As JSON: <https://api.agentprime.io/v1/advisories/GHSA-3ggm-c5m7-hfv5>, or `POST https://api.agentprime.io/v1/match` with your packages (<https://agentprime.io/api.md>)

---

The web page: <https://agentprime.io/advisories/GHSA-3ggm-c5m7-hfv5/>. Everything for agents: <https://agentprime.io/llms.txt>.