Chamilo LMS: Blind SQL Injection in model.ajax.php via filters[groupOp] authentificated
Written by anthropic/claude-haiku-5.5 from the sources below. Verify against them.
- Exploited
- No known exploitation
- Fix
- Fixed in 1.11.40, 2.0.1
- Who is exposed
- Specific setups only
Do first: Check whether your setup matches what the bug needs. Affects Chamilo LMS versions up to and including 2.0.0 The get_sessions action is called with _search=true and a crafted JSON filters parameter
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- Published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- A 0-100 score for how much a CVE matters across the industry: exploitation, exposure, how widely the software is used, severity and whether a fix exists.What do these mean? →
- 15/100 · provisional
- How many real-world setups can hit the bug, from the vendor's advisory and CISA data. It does not know your setup.What do these mean? →
- Specific setups only
- Fix
- Fixed in 1.11.40, 2.0.1
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
Summary
Chamilo LMS, an open-source learning management system, is affected by a blind SQL injection flaw that lets an authenticated administrator read, modify, or delete database records, including sensitive user and configuration data, and potentially cause denial of service through delayed queries.
Read the original description
Chamilo LMS is an open-source learning management system. Prior to 1.11.40 and 2.0.1, an authenticated administrator can call the get_sessions action in /main/inc/ajax/model.ajax.php with _search=true and a crafted JSON filters parameter whose groupOp field contains SQL syntax. Because groupOp is not restricted to the expected AND or OR operators before it is incorporated into query logic, attacker-controlled input is interpreted by the database and enables blind or time-based SQL injection. Successful exploitation can disclose sensitive user, course, session, configuration, password-reset, and administrative data, modify or delete records subject to database privileges, and cause denial of service through expensive delayed queries. This issue is fixed in versions 1.11.40 and 2.0.1.
What to do
Check whether your setup matches what the bug needs.
Affects Chamilo LMS versions up to and including 2.0.0 The get_sessions action is called with _search=true and a crafted JSON filters parameterUpgrade to a fixed version: 1.11.40, 2.0.1.
Timeline
- CVE published
- First seen by cve.now
Affected versions
- chamilo chamilo-lms
fixed in 1.11.40; From 2.0.0 · fixed in 2.0.1
Evidence 5
- Advisory
- Repository
- Repository
- Repository
- Repository
Corrections
None so far.
Something wrong on this page? Report an error. Every fix is listed here.
Questions about CVE-2026-45146
What does this mean?
A crafted filters parameter sent to the model.ajax.php endpoint is not sanitized before it reaches the database, allowing blind or time-based SQL injection. An attacker can use this to extract sensitive data from the Chamilo database, modify or delete records depending on the database privileges, or slow the system with delayed queries.Source: github.com
Am I affected, and how do I check?
Chamilo LMS versions up to and including 2.0.0 are affected, specifically when the get_sessions action is called with _search=true and a crafted JSON filters parameter. Check your installed version in the Chamilo administration panel or the package version before deciding what applies to your installation.Source: github.com
What should I do about it?
Upgrade to Chamilo LMS 1.11.40 if you are on the 1.11 branch, or to 2.0.1 if you are on the 2.0 branch. No workaround is listed in the facts.Source: github.com
Is it being exploited?
It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.Source: cve.now feed data