top of page

Chamilo LMS 2.0.0 Lets Anyone Write a PHP File to Your Web Root Through a Leftover Upload Script. VulnCheck's Canaries Now See It Exploited. Upgrade and Check public/ Today

Writer: Patrick Duggan
Patrick Duggan
3 hours ago
5 min read

What to do first. If you run Chamilo LMS 2.0.0, upgrade today. Version 2.0.1 fixes CVE-2026-45140, but Chamilo has published more than 20 later advisories against the 2.0 line since then, and five on November 17 are marked fixed only in 3.0.0, so go to the current release, 3.0.2 (November 3, 2026). If you must stay on 2.0, run 2.0.4. If you cannot upgrade this hour, block web access to public/plugin/CStudio/editor/import-project/inc/big-upload.php at your web server or reverse proxy, or delete the public/plugin/CStudio folder if you do not use the CStudio course editor. Then assume you may already have been hit and run the checks in "Am I affected?" below, because the bug lets a stranger write any file, including a PHP web shell, into your public web folder without logging in.



What is confirmed


  • The bug. Chamilo's own GitHub advisory, GHSA-g4c3-4g96-6g4m, published Tuesday June 9, 2026, is titled "Unauthenicated RCE v2.0.0" [sic] and says, in full under Impact: "Ability to run arbitrary code on the server without authentication." It is rated critical, CVSS 3.1 9.8, credited to the researcher h4knet, and lists the affected range as 2.0.0 and the patched version as 2.0.1. NVD's record (published September 17) words it as "prior to 2.0.1".

  • The fix shipped in May. Chamilo released 2.0.1 on Friday May 8, 2026. The fix is commit 4bdba1b, dated April 24, titled "Security: Plugin: CStudio: Sanitize file upload inputs to prevent malicious file names and enforce session-based validation for upload flow". It changes one script: public/plugin/CStudio/editor/import-project/inc/big-upload.php.

  • What the script did wrong, from the diff. In 2.0.0 the script had no login check at all. It took a "key" value from the request, glued it onto its temporary upload folder with no cleaning, and with action=upload appended the raw request body to that file. A key containing "../" walks out of the temporary folder and into public/, where a file ending in .php runs as code. The fix adds a 403 for anyone without a Chamilo session, strips dangerous characters and extensions from the key and the file name, and stops trusting a file name sent with the "finish" step.

  • A public exploit has existed for two months. A researcher published a write-up and a working lab exploit on GitHub (abraxas/CVE-2026-45140) on September 18, 2026. It describes exactly that path: POST to the CStudio big-upload.php script with action=upload and a traversing key, then fetch the written file. Our PoC harvester picked it up on September 21. A public PoC is when an exploit went public, not a sighting of attacks.

  • Exploitation: one source, VulnCheck. VulnCheck added CVE-2026-45140 to its KEV list with a date_added of Thursday November 19, 2026, and marks it as reported exploited by VulnCheck's own canaries. VulnCheck's date_added is the date of its earliest exploitation evidence, not the day the list changed. We could not read the canary detail itself (it sits behind a VulnCheck subscription we do not have), so we cannot tell you how many sightings, from where, or what was dropped.

  • CISA has not listed it. CVE-2026-45140 is not in CISA's Known Exploited Vulnerabilities JSON as of November 19, and CISA's SSVC note on the NVD record (September 18) said exploitation "none". That note predates VulnCheck's sighting.


Who is exposed


  • Chamilo 2.0.0. This is the version the advisory names. The 2.0 line only went stable on April 14, 2026, so 2.0.0 had less than four weeks as the newest release before 2.0.1 replaced it. Installs that went up in that window and were never updated are the population at risk.

  • 2.0 pre-releases. NVD says "prior to 2.0.1". If you run an alpha, beta or release candidate of 2.0 and the file public/plugin/CStudio/editor/import-project/inc/big-upload.php exists, treat it as vulnerable.

  • Chamilo 1.11.x does not ship this script. We checked the 1.11.x branch on GitHub: it has no CStudio plugin. The CStudio code itself has a loader for 1.11.x installs, so if you added CStudio to a 1.11 site by hand, look for an inc/big-upload.php without a login check. The advisory does not cover that case and we did not test it.

  • Turning the plugin off may not help. In the 2.0.0 file we read, the script does not check whether CStudio is enabled before accepting an upload; it only needs to be reachable on disk under public/. We did not test this on a live install, so block or remove the file rather than relying on the plugin setting.


Am I affected?


  1. Version. Open public/main/install/version.php on the server and read the new_version line. "2.0.0", or any 2.0 pre-release, means vulnerable. Your admin page also shows the version.

  2. The fixed script. On a patched install, public/plugin/CStudio/editor/import-project/inc/big-upload.php contains the text "Require an authenticated Chamilo session". If that line is missing, the script is the vulnerable one.

  3. Web server logs. Search your access logs (for example /var/log/apache2/access.log or /var/log/nginx/access.log, including rotated .gz files) for "big-upload.php". Any request to it from an address that is not one of your course editors is suspicious. A request with "action=upload" and a "key" containing "..", "%2e%2e" or "%2f" is an exploitation attempt. Note the time and the client IP, then look at what that IP requested right after: a GET to a new file name directly under your site root is the attacker checking that the write worked.

  4. New files in the web root. List files under public/ (and especially directly in public/ itself) changed since May 2026, and look for .php, .phtml, .phar or .txt files you did not put there. Also check the CStudio upload folders: var/upload/plugins/CStudio/editor/import-project/files/ and the cstudio_upload folder inside var/cache/. Leftover chunks there with odd names are a sign someone used the script.

  5. If you find a planted file, do not just delete it. Treat the server as compromised: take a copy for investigation, rotate the database password in .env and any other secrets the web user could read, check for new admin accounts in Chamilo, and rebuild from a clean install at the current version.


What is not known


  • Who is exploiting it and at what scale. VulnCheck is the only source of exploitation and its detail is paywalled. We found no vendor, CERT or press report of attacks.

  • How many 2.0.0 installs are still online. We did not run an internet census.

  • Indicators. None published in the sources we read: the advisory, the fix commit, NVD, CISA KEV, VulnCheck's KEV entry and the public PoC contain no attacker IPs, domains or hashes. We have added nothing to the feed for this CVE.


What our edge saw


We ran our edge check for this exploit from August 1 to November 19, 2026, matching the big-upload.php path, the PoC's traversal path, and any "chamilo" or "/plugin/CStudio" request. Results: 0 hits in 618,277 edge-blocked requests, 0 in 170,421 edge decoy (canary) hits, and 0 in 5,771 requests that reached our origin honeypot. None of the matches were our own pages. Read that narrowly: we do not run Chamilo and have no trap for its paths, so this says nobody tried this exploit against our sites, not that nobody is scanning for it.



Sources


  • Chamilo security advisory GHSA-g4c3-4g96-6g4m: github.com/chamilo/chamilo-lms/security/advisories/GHSA-g4c3-4g96-6g4m

  • Fix commit 4bdba1b9a8820bd70c0809317775d7f6eaa79844 and release v2.0.1 on github.com/chamilo/chamilo-lms

  • NVD: nvd.nist.gov/vuln/detail/CVE-2026-45140

  • VulnCheck KEV entry for CVE-2026-45140 (read via the VulnCheck API, November 19, 2026)

  • CISA KEV JSON (checked November 19, 2026: not listed)

  • Public PoC and write-up: github.com/abraxas/CVE-2026-45140 (third-party, lab use; we did not run it)


Want exploited-bug coverage like this and a blocklist you can pull for free? Register for the DugganUSA feed.




Every indicator in this post is in the feed. Free.

1.58M+ IOCs, STIX 2.1 / TAXII, 88% novel vs ThreatFox, exploited-CVE leads ahead of CISA. No credit card — a free API key in 30 seconds, and you can audit every claim above against the live endpoints.


Comments

Rated 0 out of 5 stars.
No ratings yet

Add a rating
bottom of page