# CVE-2026-34239: Chamilo Authenticated Remote Code Execution

> Authenticated users in Chamilo LMS can execute arbitrary code via the language AJAX endpoint due to insufficient authorization checks.

- **Severity:** High 7.5 (`CVSS:4.0/AV:N/AC:H/AT:N/PR:H/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 20 Jul 2026
- **Updated:** 20 Jul 2026
- **Also known as:** GHSA-4hwq-pv7c-3928

## What is CVE-2026-34239?

CVE-2026-34239 is a high-severity code injection vulnerability in chamilo-lms, published on 20 Jul 2026. An attacker needs administrator access to exploit it, with no action from the victim.

### Official description

Chamilo version 1.11.40 and earlier are vulnerable to authenticated remote code execution in the main/inc/ajax/lang.ajax.php path. This endpoint is protected only by `api_protect_course_script(true)`, which means any authenticated user enrolled in a course (student, teacher, DRH) can reach it.

Weakness: CWE-285 (Improper Authorization)

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


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

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

## Is CVE-2026-34239 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-34239 is a high-severity code injection vulnerability in chamilo-lms, published on 20 Jul 2026. An attacker needs administrator access to exploit it, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-34239 in the wild and no public exploit code.

Affected product: 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-34239/ (Markdown: https://insights.sbomify.com/CVE-2026-34239/index.md)
```

## Sources

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

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