A critical SQL injection vulnerability in MegaTKC Aero CMS 0.0.1 allows unauthenticated attackers to execute arbitrary database commands, posing a severe risk of data exfiltration.

The application fails to properly sanitize user input provided via the author parameter within GET requests. This allows an unauthenticated attacker to inject malicious SQL commands, enabling boolean-based, error-based, time-based, and UNION-based injection techniques.

Successful exploitation allows an attacker to bypass authentication mechanisms and gain unauthorized access to the underlying database. This could lead to the complete compromise of sensitive user data, administrative credentials, or application configuration, resulting in significant reputational damage and potential regulatory non-compliance. Given the CVSS score of 8.2, this vulnerability represents a high-severity threat that can be automated by remote actors.

Immediate Action: There is currently no official patch available for this vulnerability. Administrators should immediately restrict access to the affected application or disable it until a vendor-supplied security update is released.

Proactive Monitoring: Security teams should review web server access logs for suspicious patterns in GET requests, specifically monitoring for SQL keywords or unusual characters within the author parameter. Additionally, monitor database query logs for anomalous execution times or errors that may indicate injection attempts.

Compensating Controls: Deploy a Web Application Firewall (WAF) with rules configured to detect and block common SQL injection payloads targeting the author parameter.

Public Exploit Available: Yes, a published proof-of-concept exists as documented in the Exploit Database (EDB-ID: 51022) and the researcher's GitHub repository.

Due to the lack of an official patch and the availability of public exploit code, this vulnerability poses an immediate risk to any deployment of Aero CMS 0.0.1. Organizations using this software should prioritize removing the affected instance from the network or implementing robust WAF filtering to mitigate the risk of unauthorized data access.