# CVE-2026-116218: Dolibarr ERP CRM 19.0.0 before 23.0.4 SQL Injection via bankaccounts API type field


- **Severity:** High 7.2 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:L/VA:L/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 26 Oct 2026
- **Updated:** 26 Oct 2026
- **Also known as:** GHSA-m4jj-h65f-p4xj, UBUNTU-CVE-2026-116218

## What is CVE-2026-116218?

CVE-2026-116218 is a high-severity vulnerability in dolibarr, published on 26 Oct 2026. 

### Official description

Dolibarr ERP CRM 19.0.0 before 23.0.4 contains an SQL injection vulnerability that allows authenticated API users to inject SQL via the type field of the third-party bankaccounts REST endpoint. Attackers with only societe/creer permission can break out of the unescaped type value in CompanyBankAccount::create() to read password hashes and API keys via time-based blind subqueries.

Weakness: CWE-89 (Improper Neutralization of Special Elements used in an SQL Command)

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


## How do I fix CVE-2026-116218?

No fix has been published for CVE-2026-116218 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-116218 being exploited?

There is no known exploitation of CVE-2026-116218 in the wild and no public exploit code.

## Fix prompt for AI coding agents

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

What it is: CVE-2026-116218 is a high-severity vulnerability in dolibarr, published on 26 Oct 2026. 
Exploitation: There is no known exploitation of CVE-2026-116218 in the wild and no public exploit code.

Affected product: dolibarr. 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-116218/ (Markdown: https://insights.sbomify.com/CVE-2026-116218/index.md)
```

## Sources

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

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