CVE-2026-30875
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. Prior to version 1.11.36, an arbitrary file upload vulnerability in the H5P Import feature allows authenticated users with Teacher role to achieve Remote Code Execution (RCE). The H5P package validation only checks if h5p.json exists but doesn't block .htaccess or PHP files with alternative extensions. An attacker uploads a crafted H5P package containing a webshell and .htaccess that enables PHP execution for .txt files, bypassing security control. 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 confidenceChamilo LMS versions before 1.11.36 contain an arbitrary file upload vulnerability in the H5P Import feature. The H5P package validation only checks for the presence of h5p.json but fails to block malicious files like .htaccess or PHP files with alternative extensions. An authenticated Teacher can upload a crafted H5P package containing a webshell and an .htaccess file that enables PHP execution for .txt files, achieving Remote Code Execution.
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 Chamilo root directory or the admin panel for the exact version numberAffected if The installed version is lower than 1.11.36
-
Verify H5P Import feature is enabledCheck the system configuration or plugin settings for H5P integration status in the Chamilo admin panelAffected if H5P Import feature is active and accessible to Teachers
-
Confirm Teacher role permissions existReview user role assignments to determine if any accounts have Teacher-level access that can access the H5P Import functionalityAffected if There are users with Teacher role privileges in the system
-
Inspect H5P upload directories for suspicious filesExamine the H5P upload directories for unexpected .htaccess files or PHP files with unusual extensions, particularly files that enable PHP execution for non-standard extensionsAffected if Unexpected .htaccess or PHP files are found in H5P-related upload directories
A system is affected if it runs Chamilo LMS version below 1.11.36 with the H5P Import feature enabled and has users with Teacher role permissions who can upload H5P packages.
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 Chamilo LMS to version 1.11.36 or later to apply the security patch. If immediate upgrading is not feasible, temporarily disable the H5P Import feature or restrict Teacher role permissions until the patch can be deployed.
1.11.36
- 1. Back up your existing Chamilo LMS database and files before proceeding with the upgrade.
- 2. Download Chamilo LMS version 1.11.36 from the official source (https://chamilo.org).
- 3. Replace the existing Chamilo installation files with the new version 1.11.36 files, preserving your configuration and customizations.
- 4. Run the database upgrade script if provided with the new version.
- 5. Clear any cached data and verify the H5P Import functionality is working correctly.
- 6. Test that the application functions normally after the upgrade.
- 7. Verify that the vulnerability is fixed by attempting to upload a test H5P package with disallowed file types (the system should now reject .htaccess and PHP files).
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation3.0 h
- Implementation4.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,648.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-30875 — 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-30875 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