# CVE-2026-32892: OS Command Injection in Chamilo LMS 1.11.36

> Authenticated attackers can execute arbitrary OS commands via shell metacharacters in file move operations, leading to code execution as the web server user.

- **Severity:** Critical 9.1 (`CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:C/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 10 Apr 2026
- **Updated:** 14 Apr 2026
- **Also known as:** GHSA-59cv-qh65-vvrr

## What is CVE-2026-32892?

CVE-2026-32892 is a critical command injection vulnerability in Chamilo Chamilo Lms, published on 10 Apr 2026. An attacker needs administrator access to exploit it, with no action from the victim.

### Official description

Chamilo LMS is a learning management system. Prior to 1.11.38 and 2.0.0-RC.3, Chamilo LMS contains an OS Command Injection vulnerability in the file move function. The move() function in fileManage.lib.php passes user-controlled path values directly into exec() shell commands without using escapeshellarg(). When a user moves a document via document.php, the move_to POST parameter — which only passes through Security::remove_XSS() (an HTML-only filter) — is concatenated directly into shell commands such as exec("mv $source $target"). By default, Chamilo allows all authenticated users to create courses (allow_users_to_create_courses = true). Any user who is a teacher in a course (including self-created courses) can move documents, making this vulnerability exploitable by any authenticated user. The attacker must first place a directory with shell metacharacters in its name on the filesystem (achievable via Course Backup Import), then move a document into that directory to trigger arbitrary command execution as the web server user (www-data). This vulnerability is fixed in 1.11.38 and 2.0.0-RC.3.

Weakness: CWE-78 (Improper Neutralization of Special Elements used in an OS Command)

## Which versions are affected by CVE-2026-32892?

It affects 1 product.


Products: Chamilo Chamilo Lms.

## How do I fix CVE-2026-32892?

No fix has been published for CVE-2026-32892 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-32892 being exploited?

There is no known exploitation of CVE-2026-32892 in the wild and no public exploit code.

## Other vulnerabilities in Chamilo Chamilo Lms

- [CVE-2025-50187](https://insights.sbomify.com/CVE-2025-50187/): Chamilo: Evaluation of untrusted user input leads to Remote Code Execution (critical 9.8)
- [CVE-2023-34944](https://insights.sbomify.com/CVE-2023-34944/): File upload in n/a (critical 9.8)
- [CVE-2022-27423](https://insights.sbomify.com/CVE-2022-27423/): SQL injection in n/a (critical 9.8)
- [CVE-2021-35414](https://insights.sbomify.com/CVE-2021-35414/): SQL injection in n/a (critical 9.8)
- [CVE-2019-13082](https://insights.sbomify.com/CVE-2019-13082/): File upload in n/a (critical 9.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-32892 and fix it if it is affected.

What it is: CVE-2026-32892 is a critical command injection vulnerability in Chamilo Chamilo Lms, published on 10 Apr 2026. An attacker needs administrator access to exploit it, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-32892 in the wild and no public exploit code.

Affected product: Chamilo Chamilo Lms. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-32892/ (Markdown: https://insights.sbomify.com/CVE-2026-32892/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-32892
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-32892
- OSV: https://osv.dev/vulnerability/CVE-2026-32892

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-32892/
Summaries are generated and may contain mistakes; the official description above is the record.