CVE-2026-30881
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 · uneditedChamilo LMS is a learning management system. Version 1.11.34 and prior contains a SQL Injection vulnerability in the statistics AJAX endpoint. The parameters date_start and date_end from $_REQUEST are embedded directly into a raw SQL string without proper sanitization. Although Database::escape_string() is called downstream, its output is immediately neutralized by str_replace("\'", "'", ...), which restores any injected single quotes — effectively bypassing the escaping mechanism entirely. This allows an authenticated attacker to inject arbitrary SQL statements into the database query, enabling blind time-based and conditional data extraction. 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 confidenceSQL Injection in Chamilo LMS statistics AJAX endpoint where date_start and date_end parameters are passed through Database::escape_string() but then deliberately restored via str_replace("\'", "'"), neutralizing the escaping. Authenticated attackers can inject arbitrary SQL for blind time-based data extraction.
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< 1.11.36CVSS 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
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:L/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 checksWork through these to decide whether this CVE applies to you.
-
Identify the installed Chamilo LMS versionCheck the version.php file in the main directory, or look for a version marker in the administration panel under 'Platform > About' or similar. Common locations include main/inc/conf/configuration.php or a VERSION file in the root directory.Affected if The installed version is 1.11.34 or any version prior to 1.11.36
-
Locate the vulnerable statistics AJAX endpointSearch the codebase for files handling the statistics AJAX functionality. Look for files in the main/ or web/ directories that handle 'statistics' and 'AJAX' in the path or code, particularly those processing date_start and date_end parameters.Affected if The statistics AJAX endpoint exists and processes date_start/date_end parameters from $_REQUEST
-
Verify the SQL query construction in the statistics endpointInspect the PHP code handling the statistics endpoint. Search for raw SQL queries embedding date_start or date_end variables, and look for Database::escape_string() calls followed by str_replace that restores single quotes.Affected if The code shows raw SQL concatenation with date parameters and the escaping neutralization pattern via str_replace
-
Confirm the endpoint is accessible to authenticated usersReview the access control settings for the statistics AJAX endpoint. Check if the endpoint requires authentication and which user roles can access it.Affected if The endpoint is accessible to authenticated users (non-admin or lower-privileged accounts)
A system is affected if it runs Chamilo LMS version 1.11.34 or prior, has the statistics AJAX endpoint exposed, and allows authenticated users to access it.
Generated from the published advisory. Verify against your own configuration.
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 · scoped1.11.36
Upgrade to Chamilo LMS version 1.11.36 or later which contains the patched code. Review other endpoints for similar escaping bypass patterns.
1.11.36
- 1. Create a complete backup of the Chamilo LMS database and file system before proceeding with any upgrade.
- 2. Download Chamilo LMS version 1.11.36 or the latest stable release from the official Chamilo repository (https://github.com/chamilo/chamilo-lms) or the official website.
- 3. Extract the new version files and place them in the same directory as the current installation, ensuring configuration files are preserved or merged as needed.
- 4. Run the database upgrade script by accessing the upgrade URL (typically /main/install/upgrade.php) or following the command-line upgrade procedure documented in the Chamilo upgrade guide.
- 5. Verify the installation by logging in as an administrator and checking that the statistics AJAX endpoint now properly sanitizes the date_start and date_end parameters.
- 6. Test that existing functionality in the statistics module continues to work correctly after the upgrade.
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,176.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-30881 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-30881 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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