CVE
Chamilo LMS stored XSS in course description controller
- Exploited
- No known exploitation
- Fix
- Fixed in 2.1.0
- Who is exposed
- Not reported
Do first: Upgrade to a fixed version: 2.1.0.
Summary
Chamilo LMS has a stored cross-site scripting flaw in its course description feature. A user with a teacher login can remotely save a malicious script that runs in the browser of anyone who views that course's description, including people who are not logged in, allowing session theft, credential phishing, or defacement.
Original description
Chamilo LMS is an open-source learning management system. Prior to 2.0.3, public/main/course_description/course_description_controller.php assigns contentDescription directly from a teacher's request in the Doctrine-based add and edit paths without cross-site scripting sanitization. The stored value is rendered by src/CoreBundle/Resources/views/Course/about.html.twig through description with raw output, and the /course/{id}/about route is publicly accessible. A teacher can store active content that executes when an authenticated or unauthenticated visitor views the course description, enabling session theft, credential phishing, defacement, or actions in an authenticated victim's session. This issue is fixed in version 2.0.3.
cve.now Index
- Exploitation?/40Unknown. No CISA SSVC exploitation rating yet
- Exposure3/25Reachable over the network · Unknown: No advisory context yet
- Reach?/20Unknown. No tracked technology or package matched
- Severity6.4/10CVSS 6.4
- No patch0/5No signal
What would change the score
- Would score about 64 if added to CISA KEV
- Would score about 59 if CISA's SSVC rates exploitation active
- Would score about 28 if advisories confirm default setups are exposed
What to do
Upgrade to a fixed version: 2.1.0.
Check your systems with an agent
Paste this into a coding or ops agent. It checks your systems read-only and reports a table per asset.
Check whether my systems are affected by CVE-2026-54747 (Chamilo LMS: Stored XSS in course description controller via contentDescription field), using the cve.now data below.
Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only.
What cve.now has for CVE-2026-54747 (entry last updated 2026-11-18):
Affected:
- chamilo chamilo-lms: fixed in 2.1.0
Fixed versions: 2.1.0.
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
CISA KEV: CVE-2026-54747 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-54747 only. If you also check another CVE, look up its own KEV status; never assume it from this one.
How to check:
- Installed software: check what is actually running, not what a repo declares. Read the version from each host, container image and Kubernetes node (the binary's version output, the OS package database, image layers), and check whether the conditions above hold there. Distribution packages may carry a backported fix under an older version number; confirm against the distribution's own advisory.
Verify against the linked advisories before concluding, and cite the date you read each one:
- https://github.com/chamilo/chamilo-lms/security/advisories/GHSA-jv7g-9ff9-6cc5
- https://github.com/chamilo/chamilo-lms/commit/181687053b56f86654ac8f4ba0046fd3d97464c5
- https://github.com/chamilo/chamilo-lms/releases/tag/v2.0.3
Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing.
Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action.
Entry: https://cve.now/CVE-2026-54747
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example execute with name cve.get and arguments {"id": "CVE-2026-54747"}.Timeline
- CVE published
- First seen by cve.now
Affected versions
- chamilo chamilo-lms
fixed in 2.1.0
Evidence 5
| Kind | Source |
|---|---|
| Vendor advisory 1Establishes: Affected and fixed versions. | |
| Advisory | GitHub · chamilo/chamilo-lms · Advisory GHSA-jv7g-9ff9-6cc5 |
| CVE record 2Establishes: The identifier and description. | |
| Record | CVE List · CVE-2026-54747 |
| Record | NVD · CVE-2026-54747 |
| Other links 2 | |
| Repository | GitHub · chamilo/chamilo-lms · Commit 18168705 |
| Repository | GitHub · chamilo/chamilo-lms · Release v2.0.3 |
Corrections
None so far.
Something wrong on this page? Report an error. Every fix is listed here.
Questions about CVE-2026-54747
Is CVE-2026-54747 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
Which versions are affected by CVE-2026-54747?
chamilo-lms: before 2.1.0.Source: cve.now feed data
How do I fix CVE-2026-54747?
Upgrade to a fixed version: 2.1.0.Source: cve.now feed data