How to Fix CVE-2026-22666: Dolibarr ERP/CRM < 23.0.2 Authenticated RCE via dol_eval_standard()
Related fixes
Other vulnerabilities in the same area that are worth patching alongside this one:
- How to Fix CVE-2026-35365: CWE-59: Improper Link Resolution Before File Access ('Link Following') in coreutils — CWE-59: Improper Link Resolution Before File Access ('Link Following') in coreutils
- How to Fix CVE-2026-3742: YiFang CMS D_singlePage.php update cross site scripting in CMS — YiFang CMS D_singlePage.php update cross site scripting in CMS
- How to Fix CVE-2026-2751: Sql injection in Centreon Web on Central Server , Sql injection in Centreon Web on Central Server
- How to Fix CVE-2026-42502: Cross-Site Scripting in golang.org/x/net/html , Cross-Site Scripting in golang.org/x/net/html
- How to Fix CVE-2026-5483: Insertion of sensitive information into sent flaw in Red Hat OpenShift AI (RHOAI) , Insertion of sensitive information into sent flaw in Red Hat OpenShift AI (RHOAI)
*By Sai Kiran Pandrala*
Last verified: 2026-05-25
| Severity | CVSS 8.6, High |
|---|---|
| Actively exploited? | No |
| Affected | Dolibarr ERP/CRM (0 < 23.0.2) |
| Fixed in | 23.0.2 |
| Type (CWE) | CWE-95: Improper Neutralization of Directives in Dynamically Evaluated Code ('Eval Injection') |
CVE-2026-22666 is a dolibarr erp/crm < 23.0.2 authenticated rce via dol_eval_standard() in Dolibarr ERP/CRM. The fix is to upgrade to 23.0.2 and apply the runnable commands below.
What is CVE-2026-22666?
Dolibarr ERP/CRM versions prior to 23.0.2 contain an authenticated remote code execution vulnerability in the dol_eval_standard() function that fails to apply forbidden string checks in whitelist mode and does not detect PHP dynamic callable syntax. Attackers with administrator privileges can inject malicious payloads through computed extrafields or other evaluation paths using PHP dynamic callable syntax to bypass validation and achieve arbitrary command execution via eval().
In practical terms, a successful attacker gets remote code execution on the affected system. There is no confirmed in-the-wild exploitation listed in CISA's KEV catalog at the time of writing, but the CVSS rating still warrants prompt patching.
Am I affected?
You are affected if you run Dolibarr ERP/CRM at a version listed in the Affected row above. Probe your installed build with the commands below.
# Confirm the installed version via your package manager
dpkg -l | grep -i dolibarr # Debian/Ubuntu
rpm -qa | grep -i dolibarr # RHEL/CentOS/Rocky
How to fix CVE-2026-22666
The primary fix is to upgrade to the patched build listed in the Fixed in row above (23.0.2). Pick the platform that matches your install and run the commands below.
Linux (Ubuntu / Debian)
sudo apt-get update
sudo apt-get install --only-upgrade dolibarr-erp-crm
# Confirm the installed version meets or exceeds 23.0.2
dpkg -s dolibarr-erp-crm | grep ^Version
Linux (RHEL / CentOS / Rocky)
sudo dnf upgrade --security dolibarr-erp-crm -y
rpm -q dolibarr-erp-crm
Windows (PowerShell, admin)
winget upgrade --id 'Dolibarr.DolibarrERPCRM' --silent --accept-source-agreements --accept-package-agreements
# If winget doesn't know the product, download the patched installer from the vendor and:
Start-Process -FilePath "$env:TEMP\DolibarrERPCRM-23.0.2.msi" -ArgumentList '/qn /norestart' -Wait
PowerShell script (Windows): detect, back up, upgrade, verify, log
# Run as Administrator
$ErrorActionPreference = 'Stop'
$log = "$env:ProgramData\DolibarrERPCRM-Patch-CVE-2026-22666.log"
function Write-Log($msg) { "$(Get-Date -Format s) $msg" | Tee-Object -FilePath $log -Append }
Write-Log "Starting CVE-2026-22666 remediation for Dolibarr Dolibarr ERP/CRM"
# 1. Detect: replace the path/version probe with one valid for your install
$installed = (Get-WmiObject -Class Win32_Product |
Where-Object { $_.Name -like '*Dolibarr*' } |
Select-Object -First 1 -ExpandProperty Version)
Write-Log "Detected version: $installed"
if (-not $installed) {
Write-Log "Product not installed on this host; nothing to do."
return
}
if ([version]$installed -ge [version]'23.0.2') {
Write-Log "Already at fixed version $installed; no action needed."
return
}
# 2. Backup configuration to a timestamped folder
$backup = "$env:ProgramData\DolibarrERPCRM-Backup-$(Get-Date -Format yyyyMMdd-HHmm)"
New-Item -ItemType Directory -Path $backup -Force | Out-Null
$src = "$env:ProgramFiles\Dolibarr\Dolibarr ERP/CRM"
if (Test-Path $src) { Copy-Item -Path $src -Destination $backup -Recurse -Force }
Write-Log "Backed up config to $backup"
# 3. Apply the patched installer
$installer = "$env:TEMP\DolibarrERPCRM-23.0.2.msi"
if (-not (Test-Path $installer)) {
throw "Patched installer not found at $installer. Stage it from your software repo first."
}
Start-Process msiexec.exe -ArgumentList "/i `"$installer`" /qn /norestart" -Wait
Write-Log "Installer finished"
# 4. Verify
$verify = (Get-WmiObject -Class Win32_Product |
Where-Object { $_.Name -like '*Dolibarr*' } |
Select-Object -First 1 -ExpandProperty Version)
if ([version]$verify -ge [version]'23.0.2') {
Write-Log "SUCCESS: now at $verify (>= 23.0.2)"
} else {
Write-Log "FAILURE: still at $verify after install"
exit 1
}
Bash script (Linux): detect, back up, upgrade, verify, log
#!/usr/bin/env bash
set -euo pipefail
LOG=/var/log/dolibarr-erp-crm-patch-cve-2026-22666.log
log() { echo "$(date -Iseconds) $*" | tee -a "$LOG"; }
log "Starting CVE-2026-22666 remediation for Dolibarr Dolibarr ERP/CRM"
# 1. Detect installed version (works for deb and rpm packages)
if command -v dpkg >/dev/null && dpkg -s dolibarr-erp-crm >/dev/null 2>&1; then
CURRENT=$(dpkg-query -W -f='${Version}' dolibarr-erp-crm)
PKG_MGR=apt
elif command -v rpm >/dev/null && rpm -q dolibarr-erp-crm >/dev/null 2>&1; then
CURRENT=$(rpm -q --queryformat '%{VERSION}' dolibarr-erp-crm)
PKG_MGR=dnf
else
log "dolibarr-erp-crm not installed via apt or rpm; check your package manager or vendor instructions."
exit 0
fi
log "Detected: dolibarr-erp-crm=$CURRENT (manager=$PKG_MGR)"
# 2. Backup config
BACKUP=/var/backups/dolibarr-erp-crm-$(date +%Y%m%d-%H%M)
mkdir -p "$BACKUP"
for d in /etc/dolibarr-erp-crm /etc/${pkg%%-*} ; do
[ -d "$d" ] && cp -a "$d" "$BACKUP/" && log "Backed up $d to $BACKUP"
done
# 3. Upgrade
if [ "$PKG_MGR" = apt ]; then
sudo apt-get update -y
sudo apt-get install --only-upgrade -y dolibarr-erp-crm
else
sudo dnf upgrade --security -y dolibarr-erp-crm
fi
# 4. Verify
if [ "$PKG_MGR" = apt ]; then
NEW=$(dpkg-query -W -f='${Version}' dolibarr-erp-crm)
else
NEW=$(rpm -q --queryformat '%{VERSION}' dolibarr-erp-crm)
fi
log "After upgrade: $NEW"
log "Done. Compare $NEW against 23.0.2 and restart the affected service if needed."
If you cannot patch immediately
These are runnable hardening commands. They reduce blast radius but they are not a replacement for the vendor patch.
Rate-limit and log the affected endpoint at the reverse proxy
limit_req_zone $binary_remote_addr zone=admin:10m rate=10r/m;
location /<vulnerable-path> {
limit_req zone=admin burst=5 nodelay;
access_log /var/log/nginx/admin-access.log combined;
proxy_pass http://backend;
}
How to verify the fix worked
Run the version probe again and confirm the running build matches the Fixed in row above.
dpkg -l | grep -i "dolibarr" # Debian/Ubuntu
rpm -qa | grep -i "dolibarr" # RHEL/CentOS/Rocky
Expected output: the package version should meet or exceed 23.0.2.
Re-run any vulnerability scanner you used previously and confirm the finding for CVE-2026-22666 has cleared. Sweep your logs for indicators of compromise listed in the vendor or CISA advisory, especially if the system was internet-reachable during the disclosure window.
Frequently asked questions
Is CVE-2026-22666 being actively exploited?
Not at the time of writing. It is not listed in CISA's Known Exploited Vulnerabilities catalog. That status can change, so monitor the vendor advisory and the KEV catalog if the system is exposed.
How severe is CVE-2026-22666?
CVSS rates it 8.6 (High). Use that score to set your patch priority alongside the other items in your queue.
Do I have to take Dolibarr ERP/CRM offline to apply the patch?
It depends on the deployment. High-availability or clustered installs can usually patch one node at a time with no full outage. Standalone installs typically need a short restart. Always follow the vendor's documented upgrade steps.
What if my vulnerability scanner still flags CVE-2026-22666 after I patch?
Re-run the scan after a service restart, then confirm the scanner's plugin set is up to date. Some scanners detect by banner version only and lag the official fix metadata by a release.
References
- Official vendor advisory: https://jivasecurity.com/writeups/dolibarr-remote-code-execution-cve-2026-22666
- NVD entry: https://nvd.nist.gov/vuln/detail/CVE-2026-22666
- CISA KEV catalog: https://www.cisa.gov/known-exploited-vulnerabilities-catalog
- Additional reference: https://github.com/Dolibarr/dolibarr/security/advisories/GHSA-vmvw-qq8w-wqhg
- Additional reference: https://github.com/Dolibarr/dolibarr/commit/6f425521b3e6f9f27eca05228e02093dbaa40dea
- Additional reference: https://github.com/Dolibarr/dolibarr/releases/tag/23.0.2
*Written by Sai Kiran Pandrala. Last verified 2026-05-25. Sourced from the official vendor advisory, the NVD record, and the CISA KEV listing. Always confirm against the vendor advisory before applying changes in production.*