CVE-2026-33944: societe/class/societe.class.php · Dolibarr Has SQL Injection
Affects dolibarr/dolibarrSource GCVE Database
Not known to be exploited · CVSS 8.8 High.
Data as of 27 Oct 2026, 14:42 UTC
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:HExploitation evidence
Disclosed: evidence found.
CVE published 27 Oct 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by 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
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| Packagistdolibarr/dolibarr | Affected
| Fixed in– |
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
Until an official fix is available, restrict 'Third Party: Create/Edit' permissions to trusted users only and monitor for suspicious activity. Note that Dolibarr's WAF does not block this POST-based injection, so relying solely on the WAF is insufficient.
Description
Dolibarr ERP/CRM version 23.0.0 and earlier contains a SQL Injection vulnerability in the Third Party update functionality. The vulnerability arises from the localtax1_value (lt1) and localtax2_value (lt2) parameters being concatenated directly into an SQL UPDATE statement without proper sanitization or parameterization. An authenticated user with standard 'Third Party: Create/Edit' permissions can exploit this flaw to read and modify any database data, including sensitive information such as password hashes and API keys. The vulnerability allows injection of arbitrary SQL expressions, enabling data exfiltration and potential privilege escalation. The default unsalted MD5 password hashes facilitate cracking and admin account takeover. No official patch information is provided in the input data.