Skip to main content

CVE-2026-61532chamilo chamilo-lms path traversal

Schedule itCritical9.0EPSS not scored yet

CVE-2026-61532 is a path traversal in chamilo chamilo-lms, rated critical (9.0 on CVSS 3.1).

Why this priority: Critical severity, with no exploitation signal yet.

Published · Updated · NVD status: Received

What it is

A file name from the request can climb out of the intended folder with sequences like ../, reaching files the service never meant to expose. Input decides which file the software opens, so a caller can point it elsewhere.

How it is reached

An attacker can exploit it over the network, with an ordinary user account, but someone has to act first, such as opening a file or following a link.

What an attacker gains

A successful attack can read the data it protects, change data or behaviour and take it offline. In practice, this kind of flaw lets an attacker read or write files outside the folders the service meant to expose. The damage can spread past the vulnerable component into others.

Is it being exploited?

There is no public report of exploitation yet.

What to do

  1. Upgrade chamilo chamilo-lms to a fixed version for your release line (1.11.40, 2.0.3).
  2. Until it is patched, review who holds accounts that can reach it.
  3. Warn the people who use it, and filter files and links on the way in.

Description from NVD

Chamilo LMS is an open-source learning management system. Prior to 1.11.40 and 2.0.3, src/Chamilo/CourseBundle/Component/CourseCopy/CourseRestorer.php and src/CourseBundle/Component/CourseCopy/CourseRestorer.php use paths supplied by an imported legacy course backup without consistently confining them to the extraction directory. A course teacher can import a crafted backup containing parent-directory path segments, causing file operations to write attacker-controlled content outside the intended destination, including PHP-executable or automatically loaded locations. This can result in code execution as the PHP process and compromise course data, user data, credentials, and the host. This issue is fixed in versions 1.11.40 and 2.0.3.

What this means for your architecture.

A CVE names a product. Whether it matters depends on where that product sits in your systems: what reaches it, which trust boundary it guards and what it can reach once compromised. Veriom maps your components, their relationships and your trust boundaries from your code, cloud and delivery evidence, so you can see where a component like this sits. The radar itself does not look at your systems.

Components it touches

  • File storage the service can read or write. The flaw sits between the application and the file system it can reach.
  • Application servers and the hosts they run on. The flaw sits between untrusted input and code or command execution.
  • Template engines. The flaw sits between untrusted input and code or command execution.

Trust boundaries in play

  • Authenticated network access. An account is needed, so exposure follows who can sign in: customers, partners or staff.
  • People who open files and links. Mail, chat and browsers are the delivery path.
  • Isolation between components. The impact crosses out of the vulnerable component into others it should be isolated from.
  • Between the application and the file system it can reach. An attacker who crosses it can read or write files outside the folders the service meant to expose.

Questions to answer about your own systems

  • Where does chamilo chamilo-lms run in your systems, and at which version?
  • Which of those instances can be reached from the internet or partner networks?
  • What can it reach once compromised: which data stores, secrets and services?

14-day free trial

Understand how your systems connect.

See your services, dependencies and trust boundaries in one place, with evidence from your connected environment.

Sources

  • CVE records and CVSS scores from the NVD CVE API. This product uses the NVD API but is not endorsed or certified by the NVD.
  • Exploitation status from CISA’s Known Exploited Vulnerabilities catalog.
  • Exploit likelihood from FIRST’s Exploit Prediction Scoring System (EPSS), refreshed daily.
  • Explanations are written by Veriom from fixed templates over each record’s data, not by a person reviewing each CVE. Descriptions are quoted from the records as published.