How to Fix CVE-2026-33715: Missing authentication in chamilo-lms
By Sai Kiran Pandrala. Last verified: 2026-05-25.
| Severity | 7.2 (High) |
|---|---|
| Actively exploited? | No public listing in CISA KEV |
| Affected | chamilo >= 2.0-RC.2, < 2.0-RC.3 |
| Fixed in | chamilo-lms 2.0-RC.3 |
| Type (CWE) | CWE-306: CWE-306: Missing Authentication for Critical Function |
What is CVE-2026-33715?
Chamilo LMS is an open-source learning management system. In version 2.0-RC.2, the file public/main/inc/ajax/install.ajax.php is accessible without authentication on fully installed instances because, unlike other AJAX endpoints, it does not include the global.inc.php file that performs authentication and installation-completed checks. Its test_mailer action accepts an arbitrary Symfony Mailer DSN string from POST data and uses it to connect to an attacker-specified SMTP server, enabling Server-Side Request Forgery (SSRF) into internal networks via the SMTP protocol. An unauthenticated attacker can also abuse this to weaponize the Chamilo server as an open email relay for phishing and spam campaigns, with emails appearing to originate from the server's IP address.
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 (chamilo >= 2.0-RC.2, < 2.0-RC.3). If your build sits inside that range, you are exposed and should patch.
How to fix CVE-2026-33715
The primary fix is to upgrade chamilo-lms to the patched build. Use the commands for your platform below; the patched version listed in the vendor advisory is: chamilo-lms 2.0-RC.3.
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-33715 affecting PHP
# Run as administrator. Detect -> backup -> upgrade -> verify -> log.
$ErrorActionPreference = "Stop"
$LogPath = "C:\Logs\CVE-2026-33715-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 chamilo-lms 2.0-RC.3"
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-33715 affecting PHP
# Detect -> backup -> upgrade -> verify -> log.
set -euo pipefail
LOG="/var/log/cve-2026-33715-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-33715-$(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: chamilo-lms 2.0-RC.3)"
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 chamilo-lms 2.0-RC.3. 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
Related fixes
Other vulnerabilities in the same area that are worth patching alongside this one:
- How to Fix CVE-2026-28800: Path traversal in NatroMacro — Path traversal in NatroMacro
- How to Fix CVE-2026-2929: Stack buffer overflow in DWR-M960 — Stack buffer overflow in DWR-M960
- How to Fix CVE-2026-34873: n/a (Bundle Sibling) , n/a (Bundle Sibling)
- How to Fix CVE-2026-24894: Critical Vulnerability in frankenphp , Critical Vulnerability in frankenphp
- How to Fix CVE-2026-41882: CWE-59 in IntelliJ IDEA , CWE-59 in IntelliJ IDEA
Is CVE-2026-33715 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?
7.2 (high). 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
- Official vendor advisory: https://github.com/chamilo/chamilo-lms/security/advisories/GHSA-mxc9-9335-45mc
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-33715
- https://github.com/chamilo/chamilo-lms/releases/tag/v2.0.0-RC.3
*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.*