# 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.

- **Severity:** High 8.6 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:N/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 27 Aug 2026
- **Updated:** 24 Sep 2026
- **Also known as:** GHSA-j8xc-7c27-7wj4

## 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 (Improper Neutralization of Special Elements used in an SQL Command)

## Which versions are affected by CVE-2026-81728?

It affects 1 product.


Products: 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.

## 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

- [CVE-2022-43138](https://insights.sbomify.com/CVE-2022-43138/): Dolibarr vulnerable to privilege escalation (critical 9.8)
- [CVE-2022-40871](https://insights.sbomify.com/CVE-2022-40871/): Dolibarr vulnerable to Eval Injection (critical 9.8)
- [CVE-2021-33816](https://insights.sbomify.com/CVE-2021-33816/): Dolibarr remote PHP code execution (critical 9.8)
- [CVE-2020-7995](https://insights.sbomify.com/CVE-2020-7995/): Dolibarr Improper Restriction of Excessive Authentication Attempts (critical 9.8)
- [CVE-2013-2091](https://insights.sbomify.com/CVE-2013-2091/): SQL injection in dolibarr (critical 9.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-81728 and fix it if it is affected.

What it is: 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.
Exploitation: There is no known exploitation of CVE-2026-81728 in the wild and no public exploit code.

Affected product: Dolibarr Dolibarr Erp\/Crm. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-81728/ (Markdown: https://insights.sbomify.com/CVE-2026-81728/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-81728
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-81728
- OSV: https://osv.dev/vulnerability/CVE-2026-81728

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-81728/
Summaries are generated and may contain mistakes; the official description above is the record.