dbcve.org
Chamilo LmsApplication · Chamilo

CVE-2026-1106

MEDIUM · 5.4 CVSS v3.1 Published 2026-01-18
Fix available
A fix is available. Upgrade to 2.0.0 or later.
See remediation →
60/100
Remediation priority · Elevated
Remotely reachable Zero-click

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
A security flaw has been discovered in Chamilo LMS up to 2.0.0 Beta 1. This issue affects the function deleteLegal of the file src/CoreBundle/Controller/SocialController.php of the component Legal Consent Handler. Performing a manipulation of the argument userId results in improper authorization. The attack is possible to be carried out remotely. The exploit has been released to the public and may be used for attacks. The vendor was contacted early about this disclosure but did not respond in any way.

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

Chamilo LMS up to version 2.0.0 Beta 1 contains an improper authorization vulnerability in the deleteLegal function of SocialController.php within the Legal Consent Handler component. The userId parameter can be manipulated to delete legal consents belonging to other users without proper authorization checks, representing a broken access control vulnerability exploitable remotely.

MitigationImplement proper authorization verification in the deleteLegal function to ensure the requesting user has permission to delete legal consents for the specified userId. Validate that the authenticated user is authorized to perform the delete operation on the target user's consent data.

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:< 2.0.0= 2.0.0

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
Low
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
Low
Availability
Low

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

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
    Check the version file or admin panel of your Chamilo installation. Typical locations include a version.php file in the root or config directory, or the admin dashboard version display.
    Affected if The installed version is 2.0.0 or any version prior to 2.0.0 (e.g., 1.11.x, 1.12.x, etc.)
  2. Locate SocialController.php
    Search for the file SocialController.php in your Chamilo installation, typically found in the main/inc/lib or application/portlets/social directory.
    Affected if The file exists in the installation, indicating the SocialController component is present.
  3. Verify deleteLegal function exists
    Open SocialController.php and search for the deleteLegal function definition within the Legal Consent Handler functionality.
    Affected if The deleteLegal function is found in the SocialController.php file.
  4. Check Legal Consent Handler access
    Access the Legal Consent Handler feature through the Chamilo web interface (typically under user profile or legal settings) and verify if authenticated users can access consent management.
    Affected if The Legal Consent Handler feature is enabled and accessible to regular users.
  5. Inspect authorization logic in deleteLegal
    Review the deleteLegal function code to verify if it performs authorization checks on the userId parameter before deleting consent records. Look for current_user validation or permission checks.
    Affected if The deleteLegal function lacks proper authorization validation comparing the requesting user to the target userId parameter.

You are affected if your Chamilo LMS installation is version 2.0.0 or any prior version and the deleteLegal function in SocialController.php lacks proper authorization checks on the userId parameter.

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.

From vendor data
Upgrade available Upgrade to 2.0.0 or later
Fixed in 2.0.0
Interim mitigation

Implement proper authorization verification in the deleteLegal function to ensure the requesting user has permission to delete legal consents for the specified userId. Validate that the authenticated user is authorized to perform the delete operation on the target user's consent data.

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

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-1106 — 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-2026-1106 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