Attack Chain

1. An attacker authenticates to the Chamilo LMS as a legitimate user (e.g., student).
2. The attacker crafts a malicious HTTP POST request targeting the BigUpload endpoint.
3. The request includes a key parameter specifying the desired filename, using a .pht extension.
4. The request body contains arbitrary PHP code that the attacker wants to execute on the server.
5. The Chamilo LMS application processes the request but fails to properly sanitize the .pht extension.
6. The application writes the attacker-controlled PHP code to a file with a .pht extension in the web server's document root or accessible directory.
7. The attacker sends an HTTP request to the newly created .pht file.
8. The Apache web server, if configured to process .pht files as PHP, executes the attacker-supplied code, leading to remote code execution.

Impact

Successful exploitation of CVE-2026-33704 allows an attacker to execute arbitrary code on the Chamilo LMS server. This could lead to complete system compromise, data theft, defacement of the learning platform, or further malicious activities within the network. Given the nature of an LMS, student and faculty data, including personal information and academic records, could be exposed. There are no specific victim counts available but successful exploitation grants complete control of the Chamilo LMS instance.

Recommendation

• Upgrade Chamilo LMS to version 1.11.38 or later to patch CVE-2026-33704.
• Configure the Apache web server to not execute .pht files as PHP. This mitigation can be implemented even without patching.
• Deploy the Sigma rule Chamilo_BigUpload_PHT_File_Creation to detect the creation of .pht files via the BigUpload endpoint.
• Monitor web server access logs for requests to .pht files in the Chamilo LMS web directory using the Chamilo_PHT_File_Access Sigma rule.