CVE-2026-81728 Dolibarr before 24.0.0 SQL Injection via the CSV and XLSX Import Update Keys
Attackers with import permissions can inject SQL via CSV/XLSX import keys to read arbitrary data and modify database rows.
- Exploited in the wild
- Not known
- Login needed
- Any signed-in user
- Attackable
- Over the internet
- Victim action needed
- Not needed
- Fix
- None listed
What is CVE-2026-81728?
CVE-2026-81728 is a high-severity SQL injection vulnerability in Dolibarr Dolibarr Erp\/Crm, published on 27 Aug 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Official description
Dolibarr before 24.0.0 contains a SQL injection in its CSV and XLSX import wizard. The wizard reads its update keys with GETPOST('updatekeys', 'array') in htdocs/imports/import.php, which applies only the generic alphanohtml filter: that strips HTML but leaves SQL keywords, comment markers, parentheses, spaces and quotes intact. import_insert() in htdocs/core/modules/import/import_csv.modules.php then iterates the submitted values and builds a filter with $where[] = $key.' = '.$data[$key], having first applied preg_replace('/^.*\./i', '', $key), an alias strip that does nothing to a value containing no dot. The assembled string is executed through $this->db->query(). The injected SELECT resolves the row id that the import then assigns to $lastinsertid, which becomes the WHERE target of a subsequent UPDATE, so a UNION SELECT returning an attacker-chosen integer both exfiltrates arbitrary table content and redirects which row the import overwrites; for category link tables the raw filter array is spliced into that UPDATE directly. The interface offers a fixed list of legitimate column codes but the server never checks the submitted values against it. A user holding the import permission can exploit this. Release 23.0.4 does not carry the fix; the allow-list test was added in 24.0.0.
Weakness: CWE-89
Which versions are affected by CVE-2026-81728?
It affects 1 product.
Products include Dolibarr Dolibarr Erp\/Crm.
How do I fix CVE-2026-81728?
No fix has been published for CVE-2026-81728 yet. Limit exposure of the affected software until one is available.
Use parameterised queries everywhere and never build SQL by joining strings. Upgrade affected software first; a web application firewall only buys time. More about SQL injection.
Is CVE-2026-81728 being exploited?
There is no known exploitation of CVE-2026-81728 in the wild and no public exploit code.
Other vulnerabilities in Dolibarr Dolibarr Erp\/Crm
Sources
Also known as GHSA-j8xc-7c27-7wj4.