File Upload Flaws in Laravel CMS Components Expose Servers to Code Execution
Vulnerability Disclosure · 2 sources · Updated 5mo ago · First seen Mar 27, 2026

Two high-severity file upload vulnerabilities have been disclosed in Laravel ecosystem components used for content and file management. Sharp versions prior to 9.20.0 are affected by CVE-2026-33687, which lets authenticated users bypass upload restrictions by tampering with a client-controlled validation_rule parameter so the server accepts files without intended MIME type or extension checks. The issue was fixed in 9.20.0 by removing client-side control over validation and enforcing checks server-side; the advisory also notes risk is reduced when uploads are stored on a strictly private disk and that default setups do not directly execute uploaded PHP files unless a public disk is configured.
A separate disclosure, CVE-2019-25673, affects UniSharp Laravel File Manager v2.0.0-alpha7 and v2.0, where authenticated attackers can submit multipart uploads with the type parameter set to Files, upload malicious PHP content, and then trigger arbitrary code execution by accessing the uploaded file from the working directory path. Both issues are classified as CWE-434 unrestricted file upload flaws and carry high-impact severity scores, underscoring the risk that authenticated upload features in Laravel-based management tools can be abused to place attacker-controlled files on servers.


