A critical file upload vulnerability in the Code16 Sharp framework allows authenticated users to bypass security controls, potentially leading to unauthorized file execution.

This vulnerability involves an insecure implementation of file validation within the ApiFormUploadController, where the validation_rule parameter is improperly handled. An authenticated attacker can manipulate this parameter to bypass all MIME type and file extension restrictions.

The ability to upload arbitrary files poses a significant risk to the integrity and availability of the application. An attacker could potentially upload malicious scripts to achieve remote code execution, leading to full system compromise, data theft, or unauthorized modification of application content. Given the CVSS score of 8.8, this represents a high severity risk that requires immediate attention to prevent potential business disruption.

Immediate Action: Update the Code16 Sharp package to version 9.20.0 or later, which removes client-controlled validation rules in favor of strict server-side enforcement.

Proactive Monitoring: Review application access logs for unusual POST requests directed at the ApiFormUploadController and monitor storage directories for unexpected file types or extensions.

Compensating Controls: Ensure that the storage disk configured for Sharp uploads is set to a private location and is not directly accessible via a public web URL to prevent the execution of uploaded files.

Public Exploit Available: Unknown

The vulnerability in Code16 Sharp presents a clear path for attackers to bypass security restrictions and gain unauthorized control over the server environment. Security teams should prioritize upgrading to version 9.20.0 immediately to eliminate this attack vector. If an immediate update is not feasible, ensure that upload storage configurations are restricted to prevent direct file execution.