Answer in brief
CVE-2026-33944 records a High severity (CVSS 8.8) vulnerability in Dolibarr: SQL Injection in societe/class/societe.class.php via localtax1_value parameter. The current sources do not mark it as known exploited. The current feed maps dolibarr/dolibarr (composer), dolibarr/dolibarr (composer), dolibarr/dolibarr (composer), dolibarr/dolibarr (composer) and additional mapped packages. Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
CVSS is 8.8. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps dolibarr/dolibarr (composer), dolibarr/dolibarr (composer), dolibarr/dolibarr (composer), dolibarr/dolibarr (composer) and additional mapped packages. Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| dolibarr/dolibarrcomposer | <=23.0.0 | Not reported |
| dolibarr/dolibarrcomposer | <22.0.5 | 22.0.5 |
| dolibarr/dolibarrcomposer | >=23.0.0,<23.0.2 | 23.0.2 |
| dolibarr/dolibarrcomposer | <22.0.5 | 22.0.5 |
| dolibarr/dolibarrcomposer | >=23.0.0,<23.0.2 | 23.0.2 |
| Dolibarr/dolibarrgeneric | <22.0.5 || >=23.0.0 <23.0.2 | 22.0.5, 23.0.2 |
| dolibarr/dolibarrpackagist | >=0 | Not reported |
| dolibarr/dolibarrpackagist | >=0 <22.0.5 | 22.0.5 |
| dolibarr/dolibarrpackagist | >=23.0.0 <23.0.2 | 23.0.2 |
Published upstream
Nov 5, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Nov 5, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Oct 27, 2026
Dolibarr is an open-source enterprise resource planning and customer relationship management application. Prior to 22.0.5 and 23.0.1, there is a SQL injection vulnerability in the Third Party company update functionality. The application concatenates the localtax1_value and localtax2_value properties into an SQL UPDATE statement without numeric conversion or other appropriate sanitization. An authenticated user with Third Party create or edit permission can submit crafted lt1 or lt2 POST parameters to read sensitive database information, including password hashes, API keys, and business data, or modify third-party records. This issue is fixed in versions 22.0.5 and 23.0.2.
Quoted source text, attributed separately from HOL analysis.