# CVE-2026-93352: Laravel-Mediable 7.0.0 < 7.0.2 RCE via .pht File Upload

> Attackers can upload .pht files to achieve remote code execution due to an incomplete blocklist in Laravel-Mediable.

- **Severity:** Critical 9.3 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 23 Sep 2026
- **Updated:** 26 Sep 2026
- **Also known as:** GHSA-phwc-h4xx-5vvv

## What is CVE-2026-93352?

CVE-2026-93352 is a critical vulnerability in plank laravel-mediable, published on 23 Sep 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Laravel-Mediable 7.0.0 before 7.0.2 contains an incomplete patch for CVE-2026-49972 in which the .pht extension is absent from the forbidden_extensions blocklist in config/mediable.php. The blocklist introduced to address CVE-2026-49972 includes phpt but omits pht, which Apache executes as PHP via the default FilesMatch directive on Debian and Ubuntu systems. An attacker can upload a .pht file that passes all validation in MediaUploader::verifyExtension() and File::sanitizeFileName() because pht is not present in the blocklist, causing the file to be written to disk and executed as PHP when requested, enabling remote code execution with the privileges of the web server process.

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

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


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

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

## Is CVE-2026-93352 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-93352 is a critical vulnerability in plank laravel-mediable, published on 23 Sep 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-93352 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-93352/ (Markdown: https://insights.sbomify.com/CVE-2026-93352/index.md)
```

## Sources

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

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