dbcve.org
Chamilo LmsApplication · Chamilo

CVE-2026-28430

CRITICAL · 9.8 CVSS v3.1 Published 2026-03-16
Fix available
A fix is available. Upgrade to 1.11.34 or later.
See remediation →
100/100
Remediation priority · Urgent
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.34, there is an unauthenticated SQL injection vulnerability which allows remote attackers to execute arbitrary SQL commands via the custom_dates parameter. By chaining this with a predictable legacy password reset mechanism, an attacker can achieve full administrative account takeover without any prior credentials. The vulnerability also exposes the entire database, including PII and system configurations. 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

Unauthenticated SQL injection in the custom_dates parameter of Chamilo LMS prior to version 1.11.34 allows remote attackers to execute arbitrary SQL commands. When chained with a predictable legacy password reset mechanism, this enables full administrative account takeover without any credentials.

MitigationUpgrade Chamilo LMS to version 1.11.34 or later to patch the SQL injection 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.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
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/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
    Locate the version file or admin panel in the Chamilo installation and compare the version number to the affected range (anything below 1.11.34)
    Affected if Installed version is lower than 1.11.34
  2. Confirm custom_dates parameter handling
    Review the application source code or HTTP traffic logs to determine if the custom_dates parameter is processed by the application
    Affected if custom_dates parameter is accepted and processed by the application without proper sanitization
  3. Check legacy password reset mechanism
    Examine the authentication configuration or attempt to access the legacy password reset endpoint to determine if the predictable mechanism is active
    Affected if Legacy password reset is enabled and accessible to unauthenticated users
  4. Verify SQL injection vulnerability
    If custom_dates is in use, test the parameter with a benign SQL injection test payload (e.g., custom_dates=1' AND 1=1--) to observe if the application reflects unsanitized input in database queries
    Affected if The custom_dates parameter reflects SQL syntax in responses or produces database errors indicating unsanitized input

The environment is affected if Chamilo LMS version is below 1.11.34 AND the custom_dates parameter is accessible and processes user input without SQL sanitization, especially when combined with an enabled legacy password reset mechanism.

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 Chamilo LMS to version 1.11.34 or later to patch the SQL injection vulnerability.

Recommended fix High confidence

1.11.34

  1. Upgrade Chamilo LMS to version 1.11.34 or later
  2. Verify the upgrade was successful by checking the admin interface version number
  3. After upgrading, test the custom_dates functionality to confirm the SQL injection is remediated
  4. Review user accounts, especially administrative accounts, for any unauthorized changes
  5. Audit database logs for any suspicious SQL queries that may indicate exploitation

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

Fix this in Chamilo Lms Scoped from the published advisory
  • Consultation6.0 h
  • Implementation4.0 h
  • Testing8.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,840
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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