The following versions are currently being supported with security updates.
| Version | Supported |
|---|---|
| 3.0.* | ✅ |
| 2.0.* | ❌ |
| 1.11.44 | (to be released) |
| 1.11.42 | ✅ |
| 1.11.40 | ✅ |
| 1.11.38 | ✅ |
| 1.11.36 | ❌ |
| 1.11.34 | ❌ |
| 1.11.32 | ❌ |
| <=1.11.30 | ❌ |
Chamilo is a multi-role platform, so whether something is a vulnerability depends on the role of the person who can trigger it. The default trust levels are:
| Role | Trust | Notes |
|---|---|---|
| Platform administrator | Full | Can do anything on the platform, including running code through plugins and themes. |
| Other administrators | Lower than administrators, higher than teachers | Can take care of some limited administrative tasks on the platform, like manage sessions, questions, or users (for HRMs). They are usually not meant to create content, though (in contrast with teachers) |
| Teacher / course manager (and session coach where they may edit) | Lower than administrators, higher than learners | Trusted to author course content and manage users in their courses. Not trusted to administer the platform or to reach data of courses they do not manage. By default, they can author and edit content, including HTML with CSS and JS. |
| Learner, invitee, anonymous visitor | Untrusted | Their input must always be filtered. |
Teachers are expected to publish rich content, so by default a teacher can store HTML, including
JavaScript, in the content they author (for example course descriptions, documents, portfolio and
wiki content). Selected code paths pass the COURSEMANAGERLOWSECURITY status to
Security::remove_XSS(). With security.teacher_use_js enabled (the default), those calls return the
content unfiltered, preserving existing installations' behaviour.
Consequence when security.teacher_use_js is enabled: script written by a teacher can run in the
browser of every user who opens that content, with that user's session. This includes administrators
who browse the course. Install Chamilo in contexts where you know who your teachers are, or reduce
this exposure as described below.
A report that only shows that a teacher can store active HTML or JavaScript in their own course content is therefore treated as a hardening request, not as a vulnerability. The following are still vulnerabilities:
- the same result for a role that is not meant to author unfiltered HTML (learners, invitees, anonymous users, or a teacher editing a course they do not manage);
- script execution in a place that is not teacher content, or content that bypasses the access checks of the course;
- any filtering that is documented as being active but does not work, including content covered by
security.teacher_use_jswhen it is disabled.
Administrators can set Administration > Configuration settings > Security > Teachers can use
JavaScript in WYSIWYG editors (security.teacher_use_js) to No. This global policy applies to
all access URLs. When disabled, calls to Security::remove_XSS() that explicitly pass
COURSEMANAGERLOWSECURITY instead run the regular COURSEMANAGER HTMLPurifier profile. Calls made
with other statuses are unaffected. Expect HTML to lose some content, such as scripts, event-handler
attributes, and some embeds. The setting defaults to Yes to preserve existing course content.
This hardening affects only code paths that actually call remove_XSS() with the low-security status.
It does not rewrite previously saved content. Course Description now filters previously stored
HTML through its list and edit-form APIs while the setting is No, without changing database
records. Other output paths must be reviewed separately; this setting is not a guarantee that
every HTML output path is filtered. Review custom themes, plugins, externally hosted HTML files,
and other output sinks separately; a Content Security Policy can provide additional defense in
depth. Test both setting values on a staging system before enforcing the restriction.
The administration settings below limit what the editor offers, but they do not filter stored content:
editor.enable_iframe_inclusion(Allow iframes in HTML Editor)editor.enabled_insertHtml(Allow insertion of widgets)editor.enabled_support_svg(SVG uploads)editor.htmlpurifier_wiki(HTMLPurifier in Wiki)
Please follow the instructions at https://github.com/chamilo/chamilo-lms/wiki/security-issues to report vulnerabilities.