CVE-2026-33704
Received Received - Intake
Arbitrary File Write in Chamilo LMS Enables Remote Code Execution

Publication date: 2026-04-10

Last updated on: 2026-04-16

Assigner: GitHub, Inc.

Description
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.
CVSS Scores
EPSS Scores
Probability:
Percentile:
Meta Information
Published
2026-04-10
Last Modified
2026-04-16
Generated
2026-05-06
AI Q&A
2026-04-10
EPSS Evaluated
2026-05-05
NVD
EUVD
Affected Vendors & Products
Showing 1 associated CPE
Vendor Product Version / Range
chamilo chamilo_lms to 1.11.38 (exc)
Helpful Resources
Exploitability
CWE
CWE Icon
KEV
KEV Icon
CWE ID Description
CWE-434 The product allows the upload or transfer of dangerous file types that are automatically processed within its environment.
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?

CVE-2026-33704 is a high-severity vulnerability in Chamilo LMS versions prior to 1.11.38 that allows any authenticated user, including students, to write arbitrary content to files on the server via the BigUpload endpoint.

The vulnerability arises because the filename is controlled by the "key" parameter, which is insufficiently validated, and the raw POST body is written directly to a file in a web-accessible directory.

While files with .php extensions are filtered and renamed to .phps to prevent execution, files with the .pht extension were not filtered and could be executed as PHP on Apache servers configured to treat .pht files as PHP scripts.

This leads to remote code execution (RCE) on affected systems. The issue was fixed in version 1.11.38 by adding .pht to the list of filtered extensions.


How can this vulnerability impact me? :

This vulnerability can have serious impacts including remote code execution on the server hosting Chamilo LMS if it is configured to execute .pht files as PHP.

An attacker with low privileges (any authenticated user) can upload malicious files that execute arbitrary code, potentially compromising the server.

Even if remote code execution is not possible, arbitrary file writes can lead to denial of service by filling disk space or planting malicious content.


How can this vulnerability be detected on my network or system? Can you suggest some commands?

This vulnerability involves arbitrary file writes via the BigUpload endpoint by authenticated users. Detection can focus on monitoring HTTP POST requests to the BigUpload endpoint that include the "key" parameter controlling filenames.

You can look for suspicious POST requests with unusual file extensions like ".pht" being uploaded, which may indicate exploitation attempts.

Example commands to detect such activity include:

  • Using web server logs (e.g., Apache) to search for POST requests to the BigUpload endpoint with ".pht" or other suspicious extensions in the "key" parameter: `grep 'POST /app/cache/BigUpload' /var/log/apache2/access.log | grep -i '.pht'`
  • Using network monitoring tools like tcpdump or Wireshark to filter HTTP POST requests containing the "key" parameter: `tcpdump -A -s 0 'tcp port 80 and (((ip[2:2] - ((ip[0]&0xf)<<2)) - ((tcp[12]&0xf0)>>2)) != 0)' | grep 'key='`
  • On the server, searching for recently created or modified files with ".pht" extension in the cache directory: `find /var/www/chamilo/app/cache/ -type f -name '*.pht' -ls`

What immediate steps should I take to mitigate this vulnerability?

The primary mitigation is to upgrade Chamilo LMS to version 1.11.38 or later, where the vulnerability is fixed by filtering the ".pht" extension to prevent execution.

If immediate upgrade is not possible, consider the following temporary mitigations:

  • Configure the web server (e.g., Apache) to not treat ".pht" files as PHP scripts by removing or disabling the handler for ".pht" extensions.
  • Restrict write permissions to the `/var/www/chamilo/app/cache/` directory to prevent unauthorized file creation.
  • Monitor and block suspicious POST requests to the BigUpload endpoint, especially those attempting to upload files with dangerous extensions.

How does this vulnerability affect compliance with common standards and regulations (like GDPR, HIPAA)?:

The vulnerability allows any authenticated user to write arbitrary files to the server, potentially leading to remote code execution or denial of service. This can compromise the integrity and availability of the system.

Such a compromise could impact compliance with standards and regulations like GDPR or HIPAA, which require protection of system integrity and availability to safeguard personal and sensitive data.

However, the provided information does not explicitly discuss compliance impacts or specific regulatory considerations.


Ask Our AI Assistant
Need more information? Ask your question to get an AI reply (Powered by our expertise)
0/70
EPSS Chart