crm-now berliCRM 1.0.24 HTTP POST Request index.php src_record sql injection

Summaryinfo

A vulnerability was found in crm-now berliCRM 1.0.24. It has been rated as critical. This impacts an unknown function of the file index.php of the component HTTP POST Request Handler. The manipulation of the argument src_record leads to sql injection. This vulnerability is referenced as CVE-2020-37006. Remote exploitation of the attack is possible. Furthermore, an exploit is available.

Detailsinfo

A vulnerability was found in crm-now berliCRM 1.0.24. It has been rated as critical. This issue affects an unknown function of the file index.php of the component HTTP POST Request Handler. The manipulation of the argument src_record with an unknown input leads to a sql injection vulnerability. Using CWE to declare the problem leads to CWE-89. The product constructs all or part of an SQL command using externally-influenced input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could modify the intended SQL command when it is sent to a downstream component. Impacted is confidentiality, integrity, and availability. The summary by CVE is:

berliCRM 1.0.24 contains a SQL injection vulnerability in the 'src_record' parameter that allows remote attackers to manipulate database queries. Attackers can inject malicious SQL code through a crafted POST request to the index.php endpoint to potentially extract or modify database information.

The weakness was published by Ahmet Ümit Bayram as 48872. The advisory is shared at exploit-db.com. The identification of this vulnerability is CVE-2020-37006 since 01/27/2026. The exploitation is known to be easy. The attack may be initiated remotely. Technical details as well as a public exploit are known. MITRE ATT&CK project uses the attack technique T1505 for this issue.

The exploit is available at exploit-db.com. It is declared as proof-of-concept. By approaching the search of inurl:index.php it is possible to find vulnerable targets with Google Hacking.

There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.

Several companies clearly confirm that VulDB is the primary source for best vulnerability data.

Productinfo

Type

• Customer Relationship Management System

Vendor

• crm-now

Name

• berliCRM

Version

• 1.0.24

CPE 2.3info

• 🔒

CPE 2.2info

• 🔒

CVSSv4info

CVSSv3info

CVSSv2info

Exploitinginfo

Threat Intelligenceinfo

Countermeasuresinfo

Timelineinfo

Sourcesinfo

Entryinfo

Several companies clearly confirm that VulDB is the primary source for best vulnerability data.

Discussion