# CVE-2026-49972: Laravel-Mediable < 7.0.0 File Upload RCE via Extension Bypass

> Unauthenticated attackers can achieve remote code execution by uploading disguised PHP files, requiring specific server configurations to execute them.

- **Severity:** High 7.7 (`CVSS:4.0/AV:N/AC:L/AT:P/PR:L/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 13 Jul 2026
- **Updated:** 15 Jul 2026
- **Also known as:** GHSA-6mqm-3932-8jfr

## What is CVE-2026-49972?

CVE-2026-49972 is a high-severity vulnerability in plank laravel-mediable, published on 13 Jul 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Laravel-Mediable before 7.0.0 contains a file upload vulnerability that allows unauthenticated attackers to achieve remote code execution by uploading a file with an embedded PHP extension disguised within a double extension such as shell.php.jpg. The PATHINFO_FILENAME extraction preserves the inner .php extension in the base name, and on misconfigured Apache or nginx servers that execute any filename containing .php as PHP, the stored file is interpreted as executable code while all MIME type, extension, and aggregate type validation checks pass due to the outer .jpg extension.

Weakness: CWE-434 (Unrestricted Upload of File with Dangerous Type)

## Which versions are affected by CVE-2026-49972?


## How do I fix CVE-2026-49972?

No fix has been published for CVE-2026-49972 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-49972 being exploited?

There is no known exploitation of CVE-2026-49972 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-49972 and fix it if it is affected.

What it is: CVE-2026-49972 is a high-severity vulnerability in plank laravel-mediable, published on 13 Jul 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-49972 in the wild and no public exploit code.

Affected product: plank laravel-mediable. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-49972/ (Markdown: https://insights.sbomify.com/CVE-2026-49972/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-49972
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-49972
- OSV: https://osv.dev/vulnerability/CVE-2026-49972

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-49972/
Summaries are generated and may contain mistakes; the official description above is the record.