Chamilo LMS CStudio upload flow allows unauthenticated remote code executionGHSA-g4c3-4g96-6g4m
CRITICALFix: chamilo/chamilo-lms@4bdba1bGHSA-g4c3-4g96-6g4m is a critical-severity (CVSS 9.8) Path Traversal vulnerability in chamilo/chamilo-lms. A fix is available for chamilo/chamilo-lms — see the affected versions and patch details below.
Exploitation Status
No confirmed exploitation observed yet
- CISA assesses this as automatable — exploitation doesn’t require manual, per-target effort, which raises the odds of mass scanning and opportunistic attacks.
- A successful exploit gives an attacker total control of the affected component, not partial access.
- CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.
Exploitation and automatability from CISA’s SSVC triage for GHSA-g4c3-4g96-6g4m.
EPSS Exploitation Probability
Probability of exploitation in the next 30 days, from FIRST.org EPSS.
How urgent is this, really
Where this sits among everything scored
Real-World Exposure
chamilo/chamilo-lmsReal-time download stats are indexed for npm and PyPI packages. This vulnerability affects Packagist packages — download data is not available via public APIs for these ecosystems.
Description
Chamilo LMS is an open-source learning management system. Prior to 2.0.1, Chamilo LMS allows an unauthenticated remote attacker to execute arbitrary code on the server. The authoritative advisory does not identify the affected endpoint, component, input, or exploitation mechanism. This issue is fixed in version 2.0.1.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 🐘Packagist | chamilo/chamilo-lms | all versions | 2.0.1composer require chamilo/chamilo-lms:^2.0.1 |
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for chamilo/chamilo-lms, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update chamilo/chamilo-lms to 2.0.1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-g4c3-4g96-6g4m is resolved across your whole dependency graph.
Workarounds
Stop passing untrusted input into the interpreter or shell: call the affected binary with an argument array rather than a composed command string, reject anything outside a strict allowlist of expected values, and run the component under an account that cannot reach beyond the work it legitimately does.
Frequently Asked Questions
Is GHSA-g4c3-4g96-6g4m in your dependencies?
Find it across Packagist, including transitive dependencies.