Skip to main content
VulnerabilityPublished

CVE-2026-116218: dolibarr · SQL Injection

Affects dolibarrSource CVE Database V5

0

Not known to be exploited · CVSS 7.2 High : upgrade to 23.0.4 soon.

Data as of 26 Oct 2026, 16:53 UTC

CVSS 4.0 base score
7.2High
How severe the flaw is on the 0–10 CVSS scale.
Patch
Available – fixed in 23.0.4
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

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 26 Oct 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

What to do

Upgrade dolibarr and dolibarr/dolibarr to 23.0.4.

Affected software

ProductAffectedFixed in
DolibarrdolibarrAffected
  • >=19.0.0 <23.0.4
Fixed in
  • 23.0.4
GitHubdolibarr/dolibarrpkg:github/dolibarr/dolibarrOther threatsAffected
  • >=19.0.0 <23.0.4
Fixed in
  • 23.0.4

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

Upgrade Dolibarr ERP CRM to version 23.0.4 or later, where this SQL injection vulnerability is fixed. No other mitigation or workaround is indicated by the vendor advisory.

Description

Dolibarr ERP CRM versions 19.0.0 up to but not including 23.0.4 contain an SQL injection vulnerability in the third-party bankaccounts REST endpoint. Authenticated API users with societe/creer permission can exploit this flaw by injecting SQL via the type field, potentially reading sensitive data such as password hashes and API keys through time-based blind subqueries. The vulnerability is fixed in version 23.0.4.

References

Community reviews

Loading reviews…