dbcve.org
Chamilo LmsApplication · Chamilo

CVE-2026-30876

MEDIUM · 5.3 CVSS v3.1 Published 2026-03-16
Fix available
A fix is available. Upgrade to 1.11.36 or later.
See remediation →
62/100
Remediation priority · Elevated
Remotely reachable No privileges 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
Chamilo LMS is a learning management system. Prior to version 1.11.36, Chamilo is vulnerable to user enumeration with valid/invalid username. This issue has been patched in version 1.11.36.

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 prior to version 1.11.36 is vulnerable to user enumeration. The application returns different responses for valid versus invalid usernames during authentication or user lookup, allowing attackers to identify which accounts exist in the system.

MitigationUpgrade to Chamilo LMS version 1.11.36 or later, which patches the user enumeration vulnerability.

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.36

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

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

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. Determine Chamilo LMS installed version
    Locate and read the version.php file in the Chamilo installation directory. Common paths include /main/inc/version.php or /app/version.php in the web root. Alternatively, access the admin dashboard and navigate to System > Administration > Platform > Check version.
    Affected if Installed version is lower than 1.11.36
  2. Verify authentication interface is accessible
    Access the Chamilo login page (typically /main/auth/login.php) without being logged in. Confirm the page loads and accepts username input.
    Affected if Login page is publicly accessible and accepts user input
  3. Test for user enumeration via login responses
    Submit a login attempt with a known-valid username (e.g., admin) and then submit another with a random/invalid username. Compare the error messages, HTTP response codes, or response timing between the two attempts.
    Affected if Error messages or responses differ between valid and invalid usernames, revealing which accounts exist in the system
  4. Test for user enumeration via password reset or user lookup
    If the forgot password feature is available, submit requests with both a valid username and an invalid username. Compare whether the system responds differently (e.g., 'email sent' vs 'user not found').
    Affected if System reveals whether a username exists through different responses in user-facing features

The environment is affected if Chamilo LMS version is below 1.11.36 AND the application returns distinguishable responses that reveal whether a username exists in the system.

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.36 or later
Fixed in 1.11.36
Interim mitigation

Upgrade to Chamilo LMS version 1.11.36 or later, which patches the user enumeration vulnerability.

Recommended fix High confidence

1.11.36

  1. 1. Back up your current Chamilo LMS database and files.
  2. 2. Download Chamilo LMS version 1.11.36 from the official repository or distribution channel.
  3. 3. Replace the existing Chamilo installation files with the new version 1.11.36 files.
  4. 4. Run any database migration scripts included in the upgrade.
  5. 5. Verify the installation by accessing the admin panel.
  6. 6. Test that the login flow no longer reveals whether a username exists via different error messages.

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

Fix this in Chamilo Lms Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing2.0 h
  • Review / QA1.0 h
9.0 hours of engineering $1,600
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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