dbcve.org
Chamilo LmsApplication · Chamilo

CVE-2025-59541

HIGH · 8.1 CVSS v3.1 Published 2026-03-06
Fix available
A fix is available. Upgrade to 1.11.34 or later.
See remediation →
88/100
Remediation priority · High
Remotely reachable No privileges

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
Chamilo is a learning management system. Prior to version 1.11.34, a Cross-Site Request Forgery (CSRF) vulnerability allows an attacker to delete projects inside a course without the victim’s consent. The issue arises because sensitive actions such as project deletion do not implement anti-CSRF protections (tokens) and GET based requests. As a result, an authenticated user (Trainer) can be tricked into executing this unwanted action by simply visiting a malicious page. This issue has been patched in version 1.11.34.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

A CSRF vulnerability in Chamilo LMS prior to version 1.11.34 allows authenticated trainers to unknowingly delete course projects. The deletion functionality lacks anti-CSRF token protection and uses GET requests for sensitive state-changing operations, enabling attackers to trick users into executing unwanted deletions by luring them to malicious pages.

MitigationUpgrade to Chamilo version 1.11.34 which implements anti-CSRF token validation for project deletion and other sensitive actions.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Chamilo LmsApplication
Affected:< 1.11.34

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
Required
Scope
Unchanged
Confidentiality
None
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:H/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify installed Chamilo LMS version
    Access the Chamilo admin panel or check the version.php file in the installation directory (commonly in main/inc or a version file in the root directory). The version is also often displayed in the footer of the admin dashboard.
    Affected if The installed version is lower than 1.11.34 (e.g., 1.11.30, 1.11.32, etc.)
  2. Verify trainer user accounts exist
    Log into the Chamilo administration panel and check the user list for accounts with 'Trainer' or 'Teacher' roles assigned. You can also query the database table that stores user roles (typically 'user' or 'user_rel_user' tables).
    Affected if There are active trainer accounts in the system - these are the users who could be exploited via CSRF
  3. Confirm course projects feature is in use
    Navigate to a course as an administrator or trainer and check if the 'Projects' tool/feature is enabled or present within any course. This is typically found under the course tools section.
    Affected if Course projects feature is enabled or has been used in any course on the LMS
  4. Check for GET-based deletion in project module
    Inspect browser network traffic when a trainer deletes a project, or review the source code of the project deletion handler (commonly in main/inc/lib/project.lib.php or similar). Look for GET requests being used for deletion actions.
    Affected if Project deletion can be performed via a GET request (URL-based) rather than requiring a POST request with anti-CSRF token

You are affected if your Chamilo LMS version is below 1.11.34 AND you have trainer accounts with access to the course projects feature.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 1.11.34 or later
Fixed in 1.11.34
Interim mitigation

Upgrade to Chamilo version 1.11.34 which implements anti-CSRF token validation for project deletion and other sensitive actions.

Recommended fix High confidence

1.11.34

  1. Download Chamilo LMS version 1.11.34 from the official repository or release channel
  2. Back up your current Chamilo installation and database before upgrading
  3. Replace the existing Chamilo files with the new version 1.11.34 files
  4. Run any database migration scripts included in the upgrade
  5. Verify the installation by logging in as a Trainer and confirming anti-CSRF tokens are now required for project deletion actions
Caveat Review the Chamilo 1.11.34 release notes for any configuration or feature changes that may affect your deployment

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Chamilo Lms Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,490
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,984.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-59541 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-59541 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data