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

Published Sep 23, 2026
·
Updated

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 forbiddenextensions 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.

Affected Software

1 affected component
packagist/plank/laravel-mediable>=7.0.0<7.0.2

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade Laravel-Mediable to a version that resolves this vulnerability.

    Fixed in 7.0.2
  2. Configuration

    Add the pht extension to the forbidden_extensions blocklist in config/mediable.php.

    Laravel-Mediable forbidden_extensions = include pht

Event History

Sep 23, 2026
CVE Published
via MITRE·09:36 PM
Data Sourced
via MITRE·09:36 PM
DescriptionSeverityWeakness

Frequently Asked Questions

1

Which deployments are realistically exposed to code execution?

Deployments using Laravel-Mediable 7.0.0 or 7.0.1 are exposed where attackers can reach an upload path handled by the affected package and uploaded files can later be requested through Apache. The described execution behavior specifically applies to Debian and Ubuntu Apache configurations whose default FilesMatch directive treats .pht files as PHP.

2

What does an attacker need to exploit this issue?

The attacker needs no authentication or user interaction if they can access a vulnerable file-upload function. They must upload a file with a .pht extension and cause the uploaded file to be requested, at which point Apache executes it as the web server process.

3

How can I determine whether an installation is affected?

Check whether the application uses packagist/plank/laravel-mediable version 7.0.0 or 7.0.1. Also inspect config/mediable.php: an affected forbidden_extensions blocklist includes phpt but does not include pht.

4

What should be done if an immediate upgrade is not possible?

Add pht to the forbidden_extensions blocklist in config/mediable.php and prevent uploaded files from being executed by Apache. Review previously uploaded files for .pht files, since any such file that is web-accessible may execute when requested.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203