CVE-2026-33687: CWE-434: Unrestricted Upload of File with Dangerous Type in code16 sharp
Sharp, a Laravel content management framework package, has a vulnerability in versions prior to 9. 20. 0 that allows authenticated users to bypass file type restrictions on uploads. The issue arises because the file upload endpoint accepts a client-controlled validation_rule parameter, which is passed directly to the Laravel validator without proper server-side checks. This enables attackers to bypass MIME type and file extension restrictions by manipulating the validation_rule parameter. The vulnerability is addressed in version 9. 20. 0 by removing client control over validation rules and enforcing strict server-side upload rules. A workaround is to ensure the storage disk for uploads is private, as default configurations prevent direct execution of uploaded PHP files unless a public disk is used.
AI Analysis
Technical Summary
CVE-2026-33687 is a high-severity vulnerability (CVSS 8.8) in the Sharp package for Laravel, affecting versions before 9.20.0. The vulnerability is due to insufficient server-side enforcement of file upload validation rules. Specifically, the ApiFormUploadController's upload endpoint accepts a client-controlled validation_rule parameter, which is passed unchecked into Laravel's validator. By sending validation_rule[]=file, an authenticated attacker can bypass all file type restrictions, potentially uploading dangerous file types. The issue is fixed in version 9.20.0 by removing client control over validation rules and strictly defining upload rules server-side. The default configuration mitigates direct execution risks by using private storage disks, but public disk configurations remain vulnerable.
Potential Impact
An authenticated user can bypass all file type restrictions on file uploads, potentially allowing the upload of dangerous file types. This could lead to high impact including full confidentiality, integrity, and availability compromise as indicated by the CVSS vector (C:H/I:H/A:H). However, direct execution of uploaded PHP files is prevented under default private storage disk configurations. If a public disk is used, the risk of remote code execution increases.
Mitigation Recommendations
Upgrade Sharp to version 9.20.0 or later, where the vulnerability is fixed by removing client-controlled validation rules and enforcing strict server-side upload validation. As a workaround, ensure that the storage disk used for uploads is configured as strictly private to prevent direct execution of uploaded files. Avoid using public disk configurations for file storage. Patch status is not explicitly stated as 'patchAvailable' but the vendor fixed the issue in version 9.20.0, so upgrading to this version or later is the official fix.
CVE-2026-33687: CWE-434: Unrestricted Upload of File with Dangerous Type in code16 sharp
Description
Sharp, a Laravel content management framework package, has a vulnerability in versions prior to 9. 20. 0 that allows authenticated users to bypass file type restrictions on uploads. The issue arises because the file upload endpoint accepts a client-controlled validation_rule parameter, which is passed directly to the Laravel validator without proper server-side checks. This enables attackers to bypass MIME type and file extension restrictions by manipulating the validation_rule parameter. The vulnerability is addressed in version 9. 20. 0 by removing client control over validation rules and enforcing strict server-side upload rules. A workaround is to ensure the storage disk for uploads is private, as default configurations prevent direct execution of uploaded PHP files unless a public disk is used.
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
CVE-2026-33687 is a high-severity vulnerability (CVSS 8.8) in the Sharp package for Laravel, affecting versions before 9.20.0. The vulnerability is due to insufficient server-side enforcement of file upload validation rules. Specifically, the ApiFormUploadController's upload endpoint accepts a client-controlled validation_rule parameter, which is passed unchecked into Laravel's validator. By sending validation_rule[]=file, an authenticated attacker can bypass all file type restrictions, potentially uploading dangerous file types. The issue is fixed in version 9.20.0 by removing client control over validation rules and strictly defining upload rules server-side. The default configuration mitigates direct execution risks by using private storage disks, but public disk configurations remain vulnerable.
Potential Impact
An authenticated user can bypass all file type restrictions on file uploads, potentially allowing the upload of dangerous file types. This could lead to high impact including full confidentiality, integrity, and availability compromise as indicated by the CVSS vector (C:H/I:H/A:H). However, direct execution of uploaded PHP files is prevented under default private storage disk configurations. If a public disk is used, the risk of remote code execution increases.
Mitigation Recommendations
Upgrade Sharp to version 9.20.0 or later, where the vulnerability is fixed by removing client-controlled validation rules and enforcing strict server-side upload validation. As a workaround, ensure that the storage disk used for uploads is configured as strictly private to prevent direct execution of uploaded files. Avoid using public disk configurations for file storage. Patch status is not explicitly stated as 'patchAvailable' but the vendor fixed the issue in version 9.20.0, so upgrading to this version or later is the official fix.
Technical Details
- Data Version
- 5.2
- Assigner Short Name
- GitHub_M
- Date Reserved
- 2026-03-23T16:34:59.932Z
- Cvss Version
- 3.1
- State
- PUBLISHED
Threat ID: 69c5ac523c064ed76fd41c2f
Added to database: 3/26/2026, 9:59:46 PM
Last enriched: 4/3/2026, 1:29:31 PM
Last updated: 5/11/2026, 5:35:25 AM
Views: 60
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.