CVE-2026-33704·PHP vulnerability
Chamilo LMS is a learning management system. Prior to 1.11.38, any authenticated user (including students) can write arbitrary content to files on the server via the BigUpload endpoint. The key parameter controls the filename and the raw POST body becomes the file content. While .php extensions are filtered to .phps, the .pht extension passes through unmodified. On Apache configurations where .pht is handled as PHP, this leads to Remote Code Execution. This vulnerability is fixed in 1.11.38.
- Severity
- high
- Software
- PHP
- Fixed in
- 1.11.38
- Published
- 2026-04-10
Affected versions
Until: 1.11.38
Fixed in: 1.11.38
How to fix this CVE
Upgrade Chamilo LMS to version 1.11.38 or later to patch the arbitrary file write vulnerability in the BigUpload endpoint. This update restricts dangerous file extensions beyond just .php, preventing attackers from uploading executable files with alternative extensions like .pht. Organizations running older versions should prioritize this update as the vulnerability allows authenticated users to execute arbitrary code on the server.
sudo dnf update phpDefensia detects this vulnerability
What an exploitation attempt looks like
Sample log line indicative of exploitation attempts:
POST /main/upload/bigupload.php.*key=.*\.pht|POST.*BigUpload.*Content-Disposition.*filename.*\.phtWAF mitigation (if patching is not yet possible)
Add this rule to your WAF to block exploitation attempts while you schedule the patch.
Block POST requests to BigUpload endpoints with filename parameters containing .pht, .phtml, .php3, .php4, .php5 extensions. Implement strict file extension whitelisting that only permits safe file types (images, documents) and rejects all executable script extensions regardless of case variation.How to check if you are affected
- Step 1: Check your Chamilo LMS version by examining the version file: cat /path/to/chamilo/main/inc/conf/version.php | grep version_name
- Step 2: Verify if the BigUpload endpoint is accessible by checking if /main/upload/bigupload.php exists and is callable by authenticated users
- Step 3: Review Apache configuration to confirm if .pht files are processed as PHP: grep -r 'AddType.*pht' /etc/apache2/
- Step 4: Confirm the patch by checking if file extension validation in BigUpload now blocks .pht uploads or renames them to .phts
FAQ
What is CVE-2026-33704?
This is a file upload vulnerability in Chamilo LMS's BigUpload endpoint that allows authenticated users to write arbitrary files to the server by bypassing PHP extension filters. On Apache servers configured to execute .pht files as PHP, attackers can achieve remote code execution.
Is CVE-2026-33704 being actively exploited?
No, this vulnerability is not currently listed in the CISA Known Exploited Vulnerabilities catalog and no public exploits are widely available, though the attack method is straightforward for authenticated users.
What versions of Chamilo LMS are affected by CVE-2026-33704?
All versions prior to 1.11.38 are vulnerable. The fix was released in version 1.11.38 and should be applied immediately.
How do I check if my server is vulnerable to CVE-2026-33704?
Run: cat /path/to/chamilo/main/inc/conf/version.php | grep version_name and verify if the version is below 1.11.38. Additionally, check if .pht file uploads are blocked by attempting to upload a test file with that extension.
Does Defensia detect CVE-2026-33704?
Yes — Defensia's CVE advisory scanner compares installed package versions against the NVD database. If Chamilo LMS is installed on a monitored server, CVE-2026-33704 will appear in your dashboard with remediation steps.
Related PHP CVEs
References
Track CVEs across your fleet automatically
Defensia scans your Linux servers and tells you exactly which ones are running vulnerable versions — including CVE-2026-33704. Free for 1 server.
Get started free