CVE
Chamilo LMS stored XSS in SCORM learning path table of contents
- Exploited
- No known exploitation
- Fix
- Fixed in 1.11.40, 2.0.3
- Who is exposed
- Not reported
Do first: Upgrade to a fixed version: 1.11.40, 2.0.3.
Summary
Chamilo LMS, an open-source learning management system, is affected by a stored cross-site scripting flaw in its learning path table of contents, triggered when a malicious SCORM package item title is imported. An attacker who can get a teacher to import a crafted package can run script in the browsers of enrolled students or administrators who view that table of contents, reached over the network after a low-privilege login and a user action such as viewing the page.
Original description
Chamilo LMS is an open-source learning management system. Prior to 1.11.40 and 2.0.3, main/lp/scormItem.class.php and public/main/lp/scormItem.class.php store an attacker-controlled title element from imsmanifest.xml without cross-site scripting sanitization when a teacher imports a SCORM package. The title reaches c_lp_item.title and is rendered by src/CoreBundle/Resources/views/LearnPath/scorm_list.html.twig through item.title with raw output while Twig auto-escaping is disabled; the default configuration does not apply the optional AI-disclosure sanitization path. Enrolled students or administrators who view the learning-path table of contents can execute the stored content in their browser sessions. This issue is fixed in versions 1.11.40 and 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
- Severity5.4/10CVSS 5.4
- No patch0/5No signal
What would change the score
- Would score about 63 if added to CISA KEV
- Would score about 58 if CISA's SSVC rates exploitation active
- Would score about 27 if advisories confirm default setups are exposed
What to do
Upgrade to a fixed version: 1.11.40, 2.0.3.
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-55503 (Chamilo LMS: Stored XSS in Learning Path TOC via malicious SCORM package item title), 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-55503 (entry last updated 2026-11-18):
Affected:
- chamilo chamilo-lms: fixed in 1.11.40; from 2.0.0, fixed in 2.0.3
Fixed versions: 1.11.40, 2.0.3.
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
CISA KEV: CVE-2026-55503 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-55503 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-xfhv-qg8r-rc7w
- https://github.com/chamilo/chamilo-lms/commit/16837ff6c2db0f7345a5508791e1c23d84d9f6d0
- https://github.com/chamilo/chamilo-lms/commit/d945ecbd448ebe20fd6b815f080a3ba08687fc5f
- https://github.com/chamilo/chamilo-lms/releases/tag/v1.11.40
- 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-55503
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-55503"}.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.3
Evidence 7
| Kind | Source |
|---|---|
| Vendor advisory 1Establishes: Affected and fixed versions. | |
| Advisory | GitHub · chamilo/chamilo-lms · Advisory GHSA-xfhv-qg8r-rc7w |
| CVE record 2Establishes: The identifier and description. | |
| Record | CVE List · CVE-2026-55503 |
| Record | NVD · CVE-2026-55503 |
| Other links 4 | |
| Repository | GitHub · chamilo/chamilo-lms · Commit 16837ff6 |
| Repository | GitHub · chamilo/chamilo-lms · Commit d945ecbd |
| Repository | GitHub · chamilo/chamilo-lms · Release v1.11.40 |
| 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-55503
Is CVE-2026-55503 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-55503?
chamilo-lms: before 1.11.40; from 2.0.0 before 2.0.3.Source: cve.now feed data
How do I fix CVE-2026-55503?
Upgrade to a fixed version: 1.11.40, 2.0.3.Source: cve.now feed data