CVE-2026-33687: Sharp has Unrestricted File Upload via Client-Controlled Validation Rules
Summary The code16/sharp Laravel admin panel package contains a vulnerability in its file upload endpoint that allows authenticated users to bypass all file type restrictions. Details The upload endpoint within the ApiFormUploadController accepts a client-controlled validationrule parameter. This parameter is directly passed into the Laravel validator without sufficient server-side enforcement.
Published Mar 25, 2026 · Updated Mar 27, 2026
Affected packages
code16/sharp
- Ecosystem
- Composer (PHP)
- Affected
- < 9.20.0
- Fixed in
- 9.20.0
- Check
composer show code16/sharp
Advisory details
From the GitHub Advisory Database (CC BY 4.0).
Summary
The code16/sharp Laravel admin panel package contains a vulnerability in its file upload endpoint that allows authenticated users to bypass all file type restrictions.
Details
The upload endpoint within the ApiFormUploadController accepts a client-controlled validation_rule parameter. This parameter is directly passed into the Laravel validator without sufficient server-side enforcement. By intercepting the request and sending validation_rule[]=file, an attacker can completely bypass all MIME type and file extension restrictions. The vulnerable code is located in src/Http/Controllers/Api/ApiFormUploadController.php at line 24.
Impact
This vulnerability leads to several critical security risks:
Attackers can upload arbitrary files, including PHP webshells, to the server. For more details on the package, visit: https://github.com/code16/sharp
MIME type and extension validation can be bypassed entirely via client-controlled rules. Review the CWE definition here: https://cwe.mitre.org/data/definitions/434.html
If the storage disk is configured to be publicly accessible, this can lead to Remote Code Execution (RCE). See the vendor repository: https://github.com/code16/sharp
(Note: Under default configurations, executing uploaded PHP files directly is not possible unless a public disk configuration is in place.)
Patches
This issue has been addressed by removing the client-controlled validation rules and strictly defining upload rules server-side. The fix is available in pull request https://github.com/code16/sharp/pull/714.
Workarounds
- Restrict Disk Access: Ensure that the storage disk used for Sharp uploads is strictly private. Under default configurations, an attacker cannot directly execute uploaded PHP files unless a public disk configuration is explicitly used. For more details on Laravel disk configurations, visit: https://laravel.com/docs/13.x/filesystem
Credits
Reported by zaurgsynv.
References
How this page is made: the data panel comes from the GitHub Advisory Database, CISA’s KEV catalog, the NVD and FIRST EPSS, and updates twice a day. No analysis has been written for this entry yet. Methodology
More Composer (PHP) vulnerabilities
All Composer (PHP) entriesCVE-2026-84974
code16/sharp: Arbitrary class instantiation through the embed_key API parameter
medium5.4Nov 12, 2026CVE-2026-84987
code16/sharp: Server-side request forgery through an unanchored autocomplete endpoint check
medium5.4Nov 12, 2026CVE-2026-61823
code16 Sharp vulnerable to stored XSS via iframe srcdoc Attribute
high7.3Sep 25, 2026CVE-2026-61825
code16/sharp has a stored XSS via data-html-content Sanitizer Bypass
high8.7Sep 25, 2026CVE-2026-53634
Sharp Missing Authorization Check in Quick Creation Command Endpoints
medium4.3Jul 8, 2026CVE-2026-44692
Authenticated Sharp users can download unrelated Laravel Storage objects through the generic download endpoint
high7.7May 15, 2026
