/

CVE-2026-45140

Severity:

CRITICAL RISK

(9.8)

Remote Code Execution (CWE-94) in Chamilo LMS Server

CVE-2026-45140

Deferred

Vulnerability type

Category:

Remote Code Execution

CWE:

CWE-22, CWE-94, CWE-219, CWE-434

Impact:

Unauthenticated arbitrary code execution and server compromise

Severity:

CRITICAL RISK

(9.8)

CVSS version:

3.1

Catch this CVE while code is being written

Detect vulnerable code directly in pull requests, so CVEs are fixed before merge.

Summary

Chamilo LMS versions before 2.0.1 contain a critical vulnerability that may allow an unauthenticated remote attacker to execute arbitrary code on the server. The available advisory does not identify the affected endpoint, input, component, or exploitation mechanism, so the exact attack path remains unspecified.

Affected context

The vulnerability affects Chamilo LMS deployments using releases before 2.0.1. Because the authoritative advisory does not specify the vulnerable endpoint or processing component, the issue should be considered relevant anywhere the application accepts and processes attacker-controlled remote requests. Exploitability depends on the undisclosed implementation flaw and the privileges available to the Chamilo service.

Exploit preconditions

  • Attack surface: A remotely reachable Chamilo LMS service - Required access: No authentication is reportedly required - Trigger point: An unspecified vulnerable request, input, or application

processing path

  • Why exploitation is possible: A flaw in the affected component may allow

attacker-controlled data to be interpreted as executable code

Why this happens

The confirmed weakness is consistent with CWE-94, Improper Control of Generation of Code. This class of defect occurs when externally influenced data reaches a code-generation, evaluation, command-dispatch, or equivalent execution path without sufficiently restricting its meaning. The advisory also references CWE-22, CWE-219, and CWE-434, but does not provide enough technical detail to determine whether path traversal, a web-root placement issue, or unrestricted file upload is the initiating mechanism.

Potential impact

  • An attacker may execute arbitrary code with the privileges of the Chamilo service.
  • The attacker could access, alter, or delete learning-management data.
  • The application and underlying server could be compromised.
  • Credentials, session data, or other stored secrets could be exposed.
  • The compromised system could be used for lateral movement or further attacks.

General mitigation guidance

Mitigation generally focuses on removing any path from untrusted input to dynamic code execution and applying secure-by-default handling for uploaded or otherwise attacker-controlled content. Common defensive patterns include strict allowlists for accepted file types and operations, storage of untrusted files outside executable web-accessible locations, canonicalized path validation, schema and content validation before processing, and disabling dynamic evaluation features. Deployments should also isolate the application, minimize its filesystem and database privileges, restrict administrative interfaces, and use read-only or separately controlled storage where practical.

How teams detect issues like this

Detection can combine static analysis for dynamic evaluation, unsafe command construction, insufficient path canonicalization, and unrestricted upload handling with code review of unauthenticated request paths. Runtime monitoring should flag unexpected file creation, executable files in upload locations, child processes launched by the web service, anomalous outbound connections, and unusual access to sensitive files. Web-application policies can restrict upload types, executable content, and dangerous request patterns. Neutral automated security review tools may help identify these patterns during development.

Sources

SourceLink
github.comgithub.com/chamilo/chamilo-lms/commit/4bdba1b9a8820bd70c0809317775d7f6eaa79844
github.comgithub.com/chamilo/chamilo-lms/releases/tag/v2.0.1
github.comgithub.com/chamilo/chamilo-lms/security/advisories/GHSA-g4c3-4g96-6g4m

Frequently asked

questions

Yes. The advisory describes exploitation by an unauthenticated remote attacker,

although it does not disclose the specific endpoint or request sequence.

No authenticated account is reportedly required. The Chamilo service must be

remotely reachable, and the attacker must be able to reach the undisclosed

vulnerable processing path.

Use a release containing the vendor's fix and eliminate any unsafe flow from

attacker-controlled input to code execution. Strictly validate inputs and

uploaded content, and keep untrusted files non-executable.

Apply secure code-generation and upload-handling patterns, enforce least

privilege, review unauthenticated endpoints, and continuously test path

validation and dynamic-execution boundaries.

Find out what's already
exploitable in your codebase.