CVE-2018-13447: Dolibarr ERP/CRM SQL Injection Vulnerability in product/card.php

Background

Dolibarr ERP/CRM is an open-source software package that provides enterprise resource planning (ERP) and customer relationship management (CRM) functionalities. It is widely used by businesses to manage various aspects of their operations, including sales, inventory, and customer interactions. The vulnerability identified in the product/card.php file of Dolibarr version 7.0.3 allows remote attackers to execute arbitrary SQL commands by exploiting the statut parameter.

Vulnerability Detail

The SQL injection vulnerability in Dolibarr ERP/CRM version 7.0.3 arises from inadequate input validation in the product/card.php file. By manipulating the statut parameter, an attacker can inject malicious SQL commands into the application's database queries. This can lead to unauthorized access, data manipulation, or even complete compromise of the system. The severity of this vulnerability is rated as CRITICAL with a CVSS score of 9.8.

composer require dolibarr/dolibarr:7.0.4

Workaround

If upgrading to the latest version is not immediately feasible, users can apply a temporary workaround by modifying the product/card.php file. It is crucial to implement proper input validation and sanitization techniques to prevent SQL injection attacks. Here is an example of how to mitigate the vulnerability by using prepared statements in PHP:

// Original vulnerable code
$statut = $_GET['statut'];
$query = "SELECT * FROM products WHERE statut = '" . $statut . "'";
$result = $db->query($query);

// Mitigated code using prepared statements
$statut = $_GET['statut'];
$query = "SELECT * FROM products WHERE statut = ?";
$stmt = $db->prepare($query);
$stmt->bind_param("s", $statut);
$stmt->execute();
$result = $stmt->get_result();

By using prepared statements, the input is automatically sanitized, preventing SQL injection attacks.

Conclusion

The SQL injection vulnerability in Dolibarr ERP/CRM version 7.0.3 can be mitigated by upgrading to version 7.0.4 or later. Users can also apply a temporary workaround by implementing proper input validation and sanitization techniques. For further assistance and support in vulnerability remediation, please contact DevNack.com.

See every vulnerability recorded for dolibarr/dolibarr →

FAQ