A SQL injection vulnerability in berliCRM 1.0.24 allows authenticated attackers to perform unauthorized database operations, posing a significant risk to data integrity.

The application is susceptible to SQL injection via the src_record parameter during a POST request to the index.php endpoint. The flaw requires the attacker to have at least low-level authenticated access to the system to successfully execute malicious SQL commands.

Successful exploitation allows an attacker to manipulate backend database queries, potentially leading to unauthorized data extraction, modification, or deletion. With a CVSS score of 8.2, this vulnerability represents a high risk to the confidentiality and integrity of business information stored within the CRM database.

Immediate Action: Since a specific vendor patch is currently unknown, administrators should restrict access to the affected index.php endpoint and monitor the application for suspicious database activity.

Proactive Monitoring: Review web server and application logs for anomalous POST requests containing SQL syntax or unusual characters directed at index.php.

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

Public Exploit Available: Yes, a published proof-of-concept exploit exists and is documented on Exploit-DB (EDB-ID: 48872).

Given the availability of a public proof-of-concept, the risk of exploitation is elevated. Organizations currently running berliCRM 1.0.24 must prioritize the implementation of compensating controls, such as WAF filtering, to block malicious input until an official vendor security update is released and applied.