⚠ Reference material — not professional advice. Test in staging, back up first, verify against your specific version. Use your own judgment for your environment.
● Critical · CVSS 9.4

How to Fix CVE-2026-23500: OS command injection in dolibarr

By Sai Kiran Pandrala. Last verified: 2026-05-25.

⚡ At a glance
Severity9.4 (Critical)
Actively exploited?No public listing in CISA KEV
AffectedDolibarr < 23.0.0
Fixed indolibarr 23.0.0
Type (CWE)CWE-78: CWE-78: Improper Neutralization of Special Elements used in an OS Command ('OS Command Injection')

What is CVE-2026-23500?

Dolibarr is an enterprise resource planning (ERP) and customer relationship management (CRM) software package. In versions prior to 23.0.0, the ODT to PDF conversion process in odf.php concatenates the MAIN_ODT_AS_PDF configuration constant directly into a shell command passed to exec() without sanitization. An authenticated administrator can inject arbitrary OS commands via this constant using command separators, achieving remote code execution as the web server user when any ODT template is generated. This issue has been fixed in version 23.0.0.

Am I affected?

Run the version check that matches your platform:


# Linux
dpkg -s php 2>/dev/null | grep -i version
rpm -q php 2>/dev/null
php --version 2>/dev/null

Compare what you see against the Affected row above (Dolibarr < 23.0.0). If your build sits inside that range, you are exposed and should patch.

How to fix CVE-2026-23500

The primary fix is to upgrade dolibarr to the patched build. Use the commands for your platform below; the patched version listed in the vendor advisory is: dolibarr 23.0.0.

Ubuntu / Debian


sudo apt-get update
sudo apt-get install --only-upgrade php
php --version 2>/dev/null || dpkg -s php | grep -i version

RHEL / CentOS / Rocky / AlmaLinux


sudo dnf upgrade --security php -y
rpm -q php

SUSE / openSUSE


sudo zypper patch --category security
rpm -q php

Complete PowerShell remediation script (Windows)


# Fix script for CVE-2026-23500 affecting PHP
# Run as administrator. Detect -> backup -> upgrade -> verify -> log.

$ErrorActionPreference = "Stop"
$LogPath  = "C:\Logs\CVE-2026-23500-fix-$(Get-Date -Format yyyyMMdd-HHmmss).log"
New-Item -ItemType Directory -Force (Split-Path $LogPath) | Out-Null
Start-Transcript -Path $LogPath -Append

try {
    Write-Host "[1/4] Detecting installed version of PHP"
    $pkg = winget list --id "PHP" 2>$null
    Write-Host $pkg

    Write-Host "[2/4] Backing up configuration"
    $backup = "C:\Backup\PHP-$(Get-Date -Format yyyyMMdd)"
    New-Item -ItemType Directory -Force $backup | Out-Null
    Get-ChildItem "C:\ProgramData\PHP" -ErrorAction SilentlyContinue |
        Copy-Item -Destination $backup -Recurse -Force -ErrorAction SilentlyContinue

    Write-Host "[3/4] Applying upgrade to dolibarr 23.0.0"
    winget upgrade --id "PHP" --silent --accept-source-agreements --accept-package-agreements
    # Fallback: Windows Update for OS-level fixes
    if ($LASTEXITCODE -ne 0) {
        Install-Module -Name PSWindowsUpdate -Force -SkipPublisherCheck -ErrorAction SilentlyContinue
        Import-Module PSWindowsUpdate
        Install-WindowsUpdate -MicrosoftUpdate -AcceptAll -IgnoreReboot
    }

    Write-Host "[4/4] Verifying patched build"
    winget list --id "PHP"
    Write-Host "Fix applied. Reboot if prompted."
    exit 0
} catch {
    Write-Error "Patch failed: $_"
    exit 1
} finally {
    Stop-Transcript
}

Complete Bash remediation script (Linux)


#!/usr/bin/env bash
# Fix script for CVE-2026-23500 affecting PHP
# Detect -> backup -> upgrade -> verify -> log.

set -euo pipefail
LOG="/var/log/cve-2026-23500-fix-$(date +%Y%m%d-%H%M%S).log"
exec > >(tee -a "$LOG") 2>&1

echo "[1/4] Detecting installed version"
if command -v dpkg >/dev/null; then
    dpkg -s php 2>/dev/null | grep -i version || echo "php not installed via dpkg"
elif command -v rpm >/dev/null; then
    rpm -q php || echo "php not installed via rpm"
fi

echo "[2/4] Backing up configuration"
BACKUP="/root/backup-cve-2026-23500-$(date +%Y%m%d)"
mkdir -p "$BACKUP"
for d in /etc/php /etc/php.d /etc/php.conf; do
    [ -e "$d" ] && cp -a "$d" "$BACKUP/" || true
done

echo "[3/4] Applying upgrade (target: dolibarr 23.0.0)"
if command -v apt-get >/dev/null; then
    apt-get update
    apt-get install --only-upgrade -y php
elif command -v dnf >/dev/null; then
    dnf upgrade --security -y php
elif command -v yum >/dev/null; then
    yum update -y php
elif command -v zypper >/dev/null; then
    zypper --non-interactive patch --category security
fi

echo "[4/4] Verifying patched build"
if command -v dpkg >/dev/null; then
    dpkg -s php 2>/dev/null | grep -i version
elif command -v rpm >/dev/null; then
    rpm -q php
fi
echo "Done. Restart any running daemons that loaded the old library."

If you can't patch immediately

If you cannot apply the patched version today, restrict exposure with one of the following runnable controls. None replace the patch.

Network restriction (Linux, nftables)


# Block inbound traffic to the affected service from untrusted networks
sudo nft add table inet filter
sudo nft 'add chain inet filter input { type filter hook input priority 0 ; }'
sudo nft 'add rule inet filter input tcp dport {443, 80} ip saddr != 10.0.0.0/8 drop'
sudo nft list ruleset

Reduce attack surface


# php is a library or shell, not a service. Restart any daemon that links it
# after applying the patch so the new code is actually loaded in memory.
sudo lsof | grep php | awk '{print $1, $2}' | sort -u
# Then restart each listed process group, or schedule a reboot at the next window.

How to verify the fix worked


# Linux
php --version 2>/dev/null || dpkg -s php | grep -i version
rpm -q php 2>/dev/null || true


# Windows
winget list | findstr /I "php"
Get-HotFix | Sort-Object InstalledOn -Descending | Select-Object -First 5

Expected: the reported version is at or above dolibarr 23.0.0. Restart any services that loaded the old library (systemctl restart <service> on Linux, restart the Windows service or reboot when prompted). For network appliances, run show version on the device and confirm the build matches the patched release.

Frequently asked questions

Other vulnerabilities in the same area that are worth patching alongside this one:

Is CVE-2026-23500 actually being exploited?

According to the data sources above, no public confirmation of in-the-wild exploitation at this time. Either way, the fix is the same: apply the vendor patch.

Do I need to reboot after patching?

For OS or kernel updates, yes. For most userland packages a systemctl restart <service> is enough. Any process that loaded the old shared library keeps using it until restarted, so when in doubt, reboot.

What is the CVSS score?

9.4 (critical). Refer to the vendor advisory for the exact vector string.

Where is the official advisory?

See the References section at the bottom of this page; the vendor's URL is the authoritative source for affected builds and patched versions.

References

*Written by Sai Kiran Pandrala. Assembled from the official vendor advisory, NVD record, and CISA KEV listing on 2026-05-25. Always confirm against the vendor's advisory before applying changes in production.*