An unauthenticated SQL injection vulnerability in cameasy Liketea 1.0.0 enables remote attackers to perform unauthorized database operations and extract sensitive information.

The application fails to sanitize user-supplied latitude and longitude parameters within the laravel/app/Http/Controllers/Front/StoreController.php file, which are then concatenated into a raw SQL query. This allows an unauthenticated attacker to manipulate the query structure to perform SQL injection.

Successful exploitation of this vulnerability can lead to full database compromise, including the unauthorized access, modification, or deletion of sensitive information such as user credentials and store data. Given the CVSS score of 7.3, this represents a significant risk that could result in severe reputational damage, regulatory non-compliance, and potential service disruption for the affected business.

Immediate Action: Update the affected installation to a patched version if available, or apply the recommended code changes by parameterizing the SQL queries within StoreController.php to prevent input concatenation.

Proactive Monitoring: Monitor application logs for abnormal POST requests to the /api/v1/front/store/list endpoint, specifically looking for SQL syntax patterns or unexpected character sequences in the lat and lng parameters.

Compensating Controls: Deploy a Web Application Firewall (WAF) with rules configured to inspect JSON payloads and block common SQL injection patterns, which can provide temporary protection while the underlying code is being remediated.

Public Exploit Available: Yes — a published proof-of-concept and detailed technical write-up exist on GitHub.

This vulnerability presents a high risk due to the ease of exploitation and the potential for total database compromise. Organizations utilizing Liketea 1.0.0 must prioritize the implementation of secure coding practices, specifically parameterizing all database queries, to eliminate this SQL injection vector immediately.